Migration (Classic-to-Current) Lead-Times

Overview

This article provides an overview of typical Classic-to-Core Migration project lead-times that CIMcloud customers experience when migrating from an older “Classic” version of Website Pipeline or CIMcloud to the latest version of the CIMcloud platform.

It also includes an explanation of the various factors that can materially impact your project lead-time.  We recommend that your Lead Project Manager and Lead Project Planner understand and account for these factors when planning your overall project schedule.

Typical Lead-Times

This is a high-level overview of what our customers typically experience with migration projects.

  • Delayed Start Date – CIMcloud can have lead-times for migration deployments between 30 days and 6 months.  Be sure to reserve a spot and understand where you are in line before planning your schedule.  See the “Your Target Start Date” section below for more details.  Expedited lead-times may be available for additional pricing if needed.
  • Once Started – The standard work can typically be completed in 1 to 3 months.
  • Extra Work – The extra work can typically add an additional 1 to 6 months to the project, depending on various factors described below.

Your Target Start Date (Scheduling “Waves”)

The portion of work that CIMcloud completes on your migration project involves skilled labor.  We are leveling the load on these resources, to insure a high quality of service is delivered, by scheduling the target start dates in “waves”.  The Migration Start Date Schedule (Waves) and Next Steps article covers why we created the waves, the current target dates for each wave, and the actions you can take now to get a head start on your project (hint: you can complete Stage 0: Preparation).

If you don’t know which wave your migration project is scheduled for, you can contact a CIMcloud Customer Success Manager.

The Migration Process (Including Extra Work)

Read this article to better understand the overall Migration process, including a definition of what “Extra Work” is and how it can impact your budget and timeline.

Lead-Time Factors

The lead-time associated with a migration project varies significantly by several factors.  These factors are listed here to assist your Project Manager in determining the overall plan / schedule for your project.

This is a summary of the key factors contributing to your lead-time.

Standard Work Lead-Time Factors

These factors impact the lead-time of the “Standard Work” on a migration project.

  • CIMcloud Impact: CIMcloud’s standard deployment backlog and implementation support capacity
    • We schedule target Start Dates (for Stage 1) in the order that clients reserve a spot for their migration.
    • We continue to invest in making migrations better and faster, but there is still a material skilled labor component involved in deploying the new platform, installing the ERP sync tool, and migrating all of your data.
    • We also have skilled labor involved in providing implementation support via our ticketing team to address questions or issues as they come up.
    • That skilled labor is scheduled using typical capacity planning techniques, but can lead to delayed target start dates (depending on the load / backlog at the time)
  • Your Impact: You team’s skills and capacity to complete your work including
    • The standard work involved in any migration project (see below for more details)

Extra Work Lead-Time Factors

These factors impact the lead-time of the “Extra Work” on a migration project.

  • CIM Pro Services Impact (if applicable): The CIM pro services backlog to address some of your “Extra Work”
    • The CIM pro services group will work with you to scope, price, and execute the extra work they can help with.
    • This may include: 1) Migration of Existing Custom Mods, 2) Deployment of a 3rd Party ERP Connector, 3) Net New Custom Mods*, and 4) Consulting on Data Reengineering* or Implementation of New Features*
    • * avoid lumping these types of extra work with migration projects if at all possible.
  • Your Impact (if applicable): You team’s skills and capacity to complete your work including
    • The new features you decide to implement
    • The data/content reengineering you decide to take on
    • The assistance with testing/punchlisting the existing custom mods you decide to migrate
    • The assistance with testing/punchlisting any net new custom mods in your scope
  • CIMcloud Impact (if applicable, less typical): CIMcloud’s R&D team lead-times to address any fringe / non-typical product use-cases that are applicable to your scope.
    • Some classic sites use rarely sold and implemented product features.
    • When these features are required, CIMcloud makes every practical effort to support them on the latest version of the platform as standard product.
    • Sometimes these fringe features, on their own or in combination with other less frequently used features, present gaps that require the CIMcloud product / R&D team(s) to address.
    • The CIMcloud product / R&D team reviews migration scopes during Stage 0 in an attempt to address these up front (and notify you of any impact on your target Start Date).
    • If these are identified (and agreed upon as feature gaps) during one of the later stages (after your Start Date), they will present delays in your schedule.  The product team will work with you to get them addressed as quickly as practical so you can resume the flow of your migration process.
  • Third Party Impact (if applicable, less typical): If any of your “extra work” (typically custom mods) requires third parties, their backlog / lead-times could impact your schedule.

Was this article helpful?

Related Articles