{"id":2337,"date":"2026-04-14T10:00:00","date_gmt":"2026-04-14T07:00:00","guid":{"rendered":"https:\/\/commerce-consulting-services.com\/en\/?p=2337"},"modified":"2026-03-24T09:45:55","modified_gmt":"2026-03-24T07:45:55","slug":"sap-commerce-cloud-migration-step-by-step","status":"publish","type":"post","link":"https:\/\/commerce-consulting-services.com\/en\/sap-commerce-cloud-migration-step-by-step\/","title":{"rendered":"Migrate from SAP Hybris to SAP Commerce Cloud: A Step-by-Step Guide"},"content":{"rendered":"

[et_pb_section fb_built=”1″ admin_label=”Hero” _builder_version=”4.27.5″ _module_preset=”default” custom_padding=”0vw||80px||false|false” locked=”off” collapsed=”on” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_row _builder_version=”4.18.0″ _module_preset=”5138c454-be54-4233-bd3b-f8e6a8747976″ global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.18.0″ _module_preset=”73121f80-a3ef-4484-8763-c3f18e3c56d2″ global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_heading title=”SAP Commerce” _builder_version=”4.27.5″ _module_preset=”f0c675ea-2574-4d0e-b725-30f8550a8550″ title_level=”h4″ title_font=”IBM Plex Sans|IBM Plex Sans Condensed_weight||on|||||” title_text_color=”#1d3557″ title_font_size=”14px” title_letter_spacing=”1px” title_line_height=”1.4em” custom_margin=”||10px||false|false” locked=”off” global_colors_info=”{%22#1d3557%22:%91%22title_text_color%22%93}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_heading title=”Migrate from SAP Hybris to SAP Commerce Cloud: A Step-by-Step Guide” _builder_version=”4.27.5″ _module_preset=”ddeb8c09-9078-4424-bc15-2efb6572e28e” title_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_post_title title=”off” meta=”off” featured_image=”on” _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_post_title][et_pb_text quote_border_color=”#457b9d” _builder_version=”4.27.5″ _module_preset=”2c55a9c4-feed-423b-9edb-ae0b5b365cac” text_font=”IBM Plex Sans|IBM Plex Sans_weight|||||||” link_font=”|IBM Plex Sans_weight|||||||” link_text_color=”#1d3557″ quote_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_2_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_3_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_4_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_5_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_6_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

With SAP Hybris on-premise mainstream maintenance ending in July 2026<\/a>, many organizations have decided that SAP Commerce Cloud (CCv2) is their forward path. It is a logical choice if you have invested heavily in SAP Commerce customizations, your team knows the platform well, and you want to stay within the SAP ecosystem.<\/p>\n

But here is the part that catches teams off guard: migrating from on-premise Hybris to SAP Commerce Cloud is not an upgrade. It is not a lift-and-shift. In many cases, it is closer to a re-implementation with the advantage of existing business logic as a reference. The infrastructure model, deployment pipeline, build process, and operational approach are fundamentally different.<\/p>\n

This guide walks through the migration step by step, based on our experience with SAP Commerce architectures across multiple industries. We will be direct about what is easy, what is hard, and where teams typically lose time and money.<\/p>\n

[\/et_pb_text][et_pb_divider _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_divider][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_heading title=”Before You Start: Setting Expectations” _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_text quote_border_color=”#457b9d” _builder_version=”4.27.5″ _module_preset=”2c55a9c4-feed-423b-9edb-ae0b5b365cac” text_font=”IBM Plex Sans|IBM Plex Sans_weight|||||||” link_font=”|IBM Plex Sans_weight|||||||” link_text_color=”#1d3557″ quote_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_2_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_3_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_4_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_5_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_6_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

Let’s establish some baseline expectations that will save you from unpleasant surprises later.<\/p>\n

Timeline:<\/strong> For a moderately complex Hybris implementation (10-30 custom extensions, 3-5 major integrations, one or two storefronts), expect 9-15 months from project kickoff to production go-live. Simpler implementations can be faster. Complex multi-country, multi-brand setups with dozens of integrations can take 18+ months.<\/p>\n

It is not 1:1:<\/strong> You will not move every line of code. You should not try. The migration is an opportunity to rationalize, simplify, and modernize. Teams that attempt a pure 1:1 copy end up fighting the cloud platform’s architecture rather than leveraging it.<\/p>\n

You need SAP Commerce Cloud expertise, not just Hybris expertise.<\/strong> If your team has only worked on-premise, budget for training or external support on CCv2-specific concepts: the Commerce Cloud Portal, manifests, environments, deployment pipelines, and cloud-specific monitoring.<\/p>\n

[\/et_pb_text][et_pb_divider _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_divider][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_heading title=”Step 1: Audit Your Current Hybris Instance” _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_text quote_border_color=”#457b9d” _builder_version=”4.27.5″ _module_preset=”2c55a9c4-feed-423b-9edb-ae0b5b365cac” text_font=”IBM Plex Sans|IBM Plex Sans_weight|||||||” link_font=”|IBM Plex Sans_weight|||||||” link_text_color=”#1d3557″ quote_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_2_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_3_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_4_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_5_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_6_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

Before planning the migration, you need a clear, honest inventory of what you are working with. This audit phase typically takes 2-4 weeks and covers three areas.<\/p>\n

Custom Extensions Inventory<\/h3>\n

Catalog every custom extension in your Hybris instance. For each one, document:<\/p>\n

    \n
  • Purpose:<\/strong> What business function does it serve?<\/li>\n
  • Complexity:<\/strong> Lines of code, number of models, number of integrations<\/li>\n
  • Usage:<\/strong> Is it actively used? When was it last modified? Does anyone actually rely on it?<\/li>\n
  • Dependencies:<\/strong> What other extensions does it depend on? What depends on it?<\/li>\n<\/ul>\n

    In our experience across multiple SAP Commerce projects, 25-40% of custom extensions in a mature Hybris instance are candidates for removal. Some were built for requirements that no longer exist. Others are workarounds for bugs that SAP has since fixed. A few are duplicates of functionality that SAP added to the platform after the custom code was written.<\/p>\n

    Integration Map<\/h3>\n

    Document every system your Hybris instance talks to:<\/p>\n

      \n
    • ERP systems (SAP ECC, S\/4HANA, or third-party)<\/li>\n
    • PIM systems (SAP Commerce built-in, Akeneo, Informatica, etc.)<\/li>\n
    • Payment gateways (PSPs, tokenization services)<\/li>\n
    • Shipping and fulfillment providers<\/li>\n
    • Marketing and analytics platforms<\/li>\n
    • CMS systems (if external to Hybris)<\/li>\n
    • Search engines (Solr, external search services)<\/li>\n
    • Custom microservices<\/li>\n<\/ul>\n

      For each integration, note the protocol (REST, SOAP, IDoc, RFC, file-based), data volumes, frequency, and whether it is synchronous or asynchronous. This map will be critical in Step 6.<\/p>\n

      Data Assessment<\/h3>\n

      Understand the size and shape of your data:<\/p>\n

        \n
      • Number of products, variants, categories<\/li>\n
      • Number of customer accounts<\/li>\n
      • Order history volume<\/li>\n
      • Content (CMS pages, media assets)<\/li>\n
      • Configuration data (promotions, pricing rules, warehousing rules)<\/li>\n<\/ul>\n

        This feeds directly into your data migration strategy and helps estimate environment sizing on CCv2.<\/p>\n

        [\/et_pb_text][et_pb_divider _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_divider][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_heading title=”Step 2: Architecture Decisions” _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_text quote_border_color=”#457b9d” _builder_version=”4.27.5″ _module_preset=”2c55a9c4-feed-423b-9edb-ae0b5b365cac” text_font=”IBM Plex Sans|IBM Plex Sans_weight|||||||” link_font=”|IBM Plex Sans_weight|||||||” link_text_color=”#1d3557″ quote_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_2_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_3_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_4_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_5_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_6_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

        This is the most important step, and the one most often rushed. The decisions you make here determine the trajectory of the entire project.<\/p>\n

        What to Keep<\/h3>\n

        Start with your differentiating business logic. The custom code that represents genuine competitive advantage or unique business processes should be migrated. If you built a sophisticated multi-warehouse allocation algorithm or a complex pricing engine that handles your specific business rules, that logic needs to come with you.<\/p>\n

        What to Rebuild<\/h3>\n

        Some code will need to be rewritten to align with CCv2 patterns. Common candidates:<\/p>\n

          \n
        • Job\/cron scheduling:<\/strong> CCv2 uses a different approach to background processing than on-premise Hybris<\/li>\n
        • File handling:<\/strong> Cloud environments handle file storage differently (no persistent local filesystem in the same way)<\/li>\n
        • Session management:<\/strong> Clustering and session handling in CCv2 follows cloud-native patterns<\/li>\n
        • Logging and monitoring:<\/strong> You will use SAP Commerce Cloud’s Dynatrace integration and log infrastructure, not your on-premise monitoring stack<\/li>\n<\/ul>\n

          What to Drop<\/h3>\n

          Be ruthless here. Every piece of code you migrate is code you will maintain forever. Common candidates for removal:<\/p>\n

            \n
          • Custom infrastructure management code (monitoring scripts, backup routines, deployment tools)<\/li>\n
          • Workarounds for on-premise performance limitations<\/li>\n
          • Legacy integrations with decommissioned systems<\/li>\n
          • Custom functionality that SAP has since added to the platform natively<\/li>\n
          • Features the business no longer uses<\/li>\n<\/ul>\n

            Storefront Decision<\/h3>\n

            If you are running the classic Accelerator storefront, you need to decide whether to migrate it as-is, move to SAP Spartacus (the Angular-based SPA storefront), or build a fully custom headless frontend. Each option has significant implications:<\/p>\n

              \n
            • Accelerator migration:<\/strong> Fastest path, but you are carrying forward a legacy architecture. SAP’s investment is clearly in Spartacus and composable storefronts.<\/li>\n
            • Spartacus:<\/strong> SAP’s strategic direction, good component library, but it is a significant frontend rewrite. Plan 3-6 months of additional effort.<\/li>\n
            • Custom headless:<\/strong> Maximum flexibility, but you own the entire frontend stack. Requires strong frontend engineering capability.<\/li>\n<\/ul>\n

              [\/et_pb_text][et_pb_divider _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_divider][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_heading title=”Step 3: Infrastructure and Environment Setup” _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_text quote_border_color=”#457b9d” _builder_version=”4.27.5″ _module_preset=”2c55a9c4-feed-423b-9edb-ae0b5b365cac” text_font=”IBM Plex Sans|IBM Plex Sans_weight|||||||” link_font=”|IBM Plex Sans_weight|||||||” link_text_color=”#1d3557″ quote_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_2_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_3_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_4_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_5_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_6_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

              SAP Commerce Cloud runs on Microsoft Azure, managed through the Commerce Cloud Portal (CCP). Your environment setup involves several components that do not exist in on-premise Hybris.<\/p>\n

              Commerce Cloud Portal<\/h3>\n

              The CCP is your management interface for environments, builds, deployments, and monitoring. Familiarize your team with it early. Allocate time for training – it is not complex, but it is different from whatever you were using before.<\/p>\n

              Environment Strategy<\/h3>\n

              CCv2 provides a defined set of environments based on your subscription tier. Typically:<\/p>\n

                \n
              • Development<\/strong> (d1, d2, etc.): For active development and integration testing<\/li>\n
              • Staging<\/strong> (s1): Pre-production validation<\/li>\n
              • Production<\/strong> (p1): Live environment<\/li>\n<\/ul>\n

                If your on-premise setup had six or seven environments for different testing phases, you will need to adapt your workflow. Some teams supplement CCv2 environments with local Docker-based development environments for faster iteration.<\/p>\n

                Manifest Configuration<\/h3>\n

                The manifest.json<\/code> file is central to CCv2 deployments. It defines your extensions, AddOns, properties, aspects (server groups), and web applications. Getting this right early prevents a lot of downstream pain.<\/p>\n

                {\n  "commerceSuiteVersion": "2211",\n  "enableImageProcessingService": true,\n  "extensions": [\n    "your-custom-extension-1",\n    "your-custom-extension-2"\n  ],\n  "useConfig": {\n    "extensions": {\n      "location": "cloud\/manifest-extensions.json"\n    },\n    "properties": [\n      {\n        "location": "cloud\/common.properties",\n        "persona": ""\n      },\n      {\n        "location": "cloud\/production.properties",\n        "persona": "production"\n      }\n    ]\n  },\n  "aspects": [\n    {\n      "name": "backoffice",\n      "properties": [\n        {\n          "key": "cluster.node.groups",\n          "value": "integration,backgroundProcessing,services"\n        }\n      ]\n    },\n    {\n      "name": "accstorefront",\n      "webapps": [\n        {\n          "name": "mediaweb",\n          "contextPath": "\/medias"\n        },\n        {\n          "name": "yourstorefront",\n          "contextPath": ""\n        }\n      ]\n    }\n  ]\n}\n<\/code><\/pre>\n
                Start with a minimal manifest and add complexity incrementally. Trying to replicate your full on-premise configuration in one go is a common source of early frustration.<\/p>\n
                [\/et_pb_text][et_pb_divider _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_divider][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_heading title=”Step 4: Code Migration and Refactoring” _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_text quote_border_color=”#457b9d” _builder_version=”4.27.5″ _module_preset=”2c55a9c4-feed-423b-9edb-ae0b5b365cac” text_font=”IBM Plex Sans|IBM Plex Sans_weight|||||||” link_font=”|IBM Plex Sans_weight|||||||” link_text_color=”#1d3557″ quote_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_2_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_3_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_4_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_5_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_6_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n
                With your architecture decisions made and your target environment configured, you can start moving code. This is the longest phase and where most of the hands-on engineering happens.<\/p>\n
                Build System Changes<\/h3>\n
                On-premise Hybris uses Ant. CCv2 also uses the standard Commerce build system, but the build is triggered through the CCP or via the CCv2 API. Your build must be reproducible from a clean checkout of your repository. If your current build depends on local tooling, scripts, or manual steps, those need to be automated or eliminated.<\/p>\n
                Repository Structure<\/h3>\n
                CCv2 expects a specific repository structure. Your custom code goes into the core-customize<\/code> directory, your JavaScript storefront (if using Spartacus) goes into js-storefront<\/code>, and cloud-specific configuration goes into designated locations. Restructuring your repository is typically a one-time effort, but it needs to be done carefully to preserve git history.<\/p>\n
                Extension Refactoring<\/h3>\n
                For each custom extension you decided to keep in Step 2, you need to:<\/p>\n
                  \n
                1. Review for cloud compatibility:<\/strong> Remove any code that assumes local filesystem access, hard-coded server addresses, or environment-specific configuration that should be externalized.<\/li>\n
                2. Update deprecated APIs:<\/strong> If you are jumping multiple Commerce versions (e.g., from 6.7 to 2211), you will encounter deprecated and removed APIs. SAP provides release notes for each version documenting breaking changes.<\/li>\n
                3. Externalize configuration:<\/strong> Properties that differ between environments should be in your manifest or properties files, not hard-coded.<\/li>\n
                4. Review ImpEx scripts:<\/strong> Essential data imports need to be reviewed for cloud compatibility. Pay special attention to file references and paths.<\/li>\n<\/ol>\n
                  Custom Build Steps<\/h3>\n
                  If your build includes custom steps (code generation, asset compilation, report generation), these need to be integrated into the standard build pipeline or handled differently. CCv2 has specific hooks for custom build phases, but they operate within constraints.<\/p>\n
                  [\/et_pb_text][et_pb_divider _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_divider][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_heading title=”Step 5: Data Migration Strategy” _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_text quote_border_color=”#457b9d” _builder_version=”4.27.5″ _module_preset=”2c55a9c4-feed-423b-9edb-ae0b5b365cac” text_font=”IBM Plex Sans|IBM Plex Sans_weight|||||||” link_font=”|IBM Plex Sans_weight|||||||” link_text_color=”#1d3557″ quote_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_2_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_3_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_4_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_5_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_6_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n
                  Data migration is often the workstream that derails timelines. It is not glamorous work, but it is essential and always more complex than initially estimated.<\/p>\n
                  What to Migrate<\/h3>\n
                  At minimum, you need to migrate:<\/p>\n