{"id":31120,"date":"2023-09-13T07:00:00","date_gmt":"2023-09-13T14:00:00","guid":{"rendered":"https:\/\/cloudinary.com\/blog\/?p=31120"},"modified":"2024-10-23T17:38:43","modified_gmt":"2024-10-24T00:38:43","slug":"cloudinary-migration-overview","status":"publish","type":"post","link":"https:\/\/cloudinary.com\/blog\/cloudinary-migration-overview","title":{"rendered":"Cloudinary Migration: An Overview of Essential Considerations"},"content":{"rendered":"\n

Organizations across industries are increasingly recognizing the need to migrate their digital media experience to keep pace with technological advancements and evolving customer expectations. Whether it’s moving from an outdated legacy system to a modern cloud-based infrastructure, or transitioning from an on-premises solution to a scalable SaaS platform, digital platform migration has become a critical strategic initiative for businesses seeking to remain competitive and agile.<\/p>\n\n\n\n

What Our Customers Say<\/h2>\n\n\n\n

That was the case for Rapha<\/a>, one of the world\u2019s best-loved cycling apparel brands. The company upgraded to Cloudinary and adopted a full MACH strategy, radically improving the way it works with and delivers visual media.<\/p>\n\n\n\n

Neiman Marcus<\/a> also chose Cloudinary when it abandoned its legacy systems, Scene7, in favor of a new image and video platform. Over the years, Cloudinary has provided ongoing support of the luxury retailer\u2019s e-commerce efforts by automating and enhancing its massive visual assets library, reducing its photoshoot-to-web time by 50%. <\/p>\n\n\n\n

The below is especially important if you\u2019re planning or recently started using Cloudinary.<\/p>\n\n\n\n

Before You Start<\/h2>\n\n\n\n

It is a high-level and general article, intended as a basis for a detailed planning of migration. Not all topics apply to your specific migration or Cloudinary plan, and there is no deep dive into any specific use case. And if you need to migrate from Scene7, make sure to read these special considerations<\/a>.<\/p>\n\n\n\n

Also not covered are setting goals, success criteria, and timelines, which are crucial to the success of any project.<\/p>\n\n\n\n

The target audience is small business owners, application managers, CTOs, marketing managers, digital asset management (DAM) managers, and any other stakeholder who can decide or manage the way digital media is used in an organization. If you work in an enterprise, then we have premium Professional Services<\/a> that will allow you to focus on your own KPIs.<\/p>\n\n\n\n

Before Go-Live<\/h2>\n\n\n\n
    \n
  1. Sign up<\/a> for a new account, if you didn\u2019t do so already. A random environment name will be generated automatically, so you would like to change it to a meaningful name, go to your Account Settings<\/a><\/strong>. Note that this change is possible only for environments with fewer than 1,000 assets.<\/li>\n\n\n\n
  2. By default, your environment is hosted in data centers in the U.S. Enterprise customers with a business core in Europe or Asia Pacific can request their customer success manager (CSM) to install the environment in the relevant geo.<\/li>\n\n\n\n
  3. The default Cloudinary delivery URLs use https:\/\/res.cloudinary.com<\/code>. It’s highly recommended to deliver media using your domain, a feature called custom CNAME and is available for premium customers. Contact Cloudinary Support<\/a> for further details.<\/li>\n\n\n\n
  4. Most customers use folders to organize their assets in Cloudinary. Here are some guidelines:
    – In most implementations, folders would appear as part of the delivery URLs, so they should be SEO friendly.
    – Permissions are granted on folder level, so different permission groups need to have different folders.
    –     User-generated content<\/a> should be in a folder of its own.<\/li>\n\n\n\n
  5. Some customers are using multiple environments with Cloudinary. The typical use cases are:
    – Separating between Development\/Staging\/Production environments.
    – Separating between different brands, companies, or cost-centers.<\/li>\n\n\n\n
  6. If you\u2019ll have multiple users working in your account, we recommend assigning them roles and folder-level permissions<\/a>.<\/li>\n\n\n\n
  7. You can log in to your local environment via social logins (Google, GitHub), SAML SSO<\/a>, and or local (app) users. If you\u2019re using the local users’ method, then it’s highly recommended to enable 2FA (two-factor authentication).<\/li>\n\n\n\n
  8. Assets backup is useful in case assets were deleted by accident, by a rogue script, etc. The automatic backup<\/a> is a no-brainer.<\/li>\n\n\n\n
  9. Cloudinary is extensible in so many ways that I can only list the links:<\/li>\n<\/ol>\n\n\n\n

    When uploading assets<\/strong>:<\/p>\n\n\n\n