Extra Work on Migrations (Classic-to-Current)

Overview

“Extra Work” is the term we use to describe several categories of additional work that extends the lead-time and typically the overall cost of a migration project.  Extra work also adds additional steps in several stages of the process. As a general rule, we highly recommend deferring as much (or all) of the extra work as practical to a future phase / project.

Target Audience for This Article

This article is intended for customers who are live on a “Classic” version of the Website Pipeline or CIMcloud platform and are migrating to the latest version of CIMcloud.

The 6 Categories of Extra Work

Extra work typically falls into these 6 categories:

Fringe Product Use-Cases/Gaps

This applies if there is a gap in the standard CIMcloud product that is exposed (typically from a rarely sold combination of features).  If this is identified as a gap, CIMcloud’s R&D teams will work with you to close the gap and make the fix available in an upcoming release.

  • A CIMcloud product manager will notify you if there are any known fringe product use cases in your scope that might impact your Start Date.

Data/Content Reengineering

This applies if you decide to overhaul part of your existing data (like overhauling your product catalog or materially changing your shipping price calculations).

  • We recommend deferring data/content reengineering to a future phase if practical (so it does not slow down and/or complication your migration project).

New Feature Implementation ($)

This applies if you deploy a net new feature (and it’s associated setup, configuration, and testing) and roll it out with the initial go live of you new platform.

  • This requires an additional billable pro services engagement.
  • We recommend deferring all new feature implementation to a future phase (so it does not slow down and/or complication your migration project).

Migration of Existing Custom Mods ($)

This applies if you work with the CIM Pro Services group to maintain capabilities you have that are not part of the current CIMcloud platform (it typically involves refactoring, installing, and testing custom code make it work with the standard platform).

  • This requires an additional billable pro services engagement.
  • We recommend only migrating customizations that are critical for business operations.
  • Your existing custom modifications are identified and decided upon via a standard 3-step process:
    • Step #1: Custom Inventory (no charge) – This is a quick / cursory inventory of what you have.
    • Step #2: Custom Audit (billable) – This is a deeper dive into you customizations to 1) verify specifically what they do, 2) determine how they could be refactored to move to the new platform, and 3) estimate the amount of work involved in moving them.  A Solution Architect will then walk through each item with you to help you determine whether you not you want it included in your scope / SOW.
    • Step #3: Custom Migration (billable) – The custom work is complete, installed on the new platform, and tested / punchlisted with you.
    • Note: In some cases, you many want to consider electing to stand up a pre-deployment platform (in Stage 0 of the project) to allow you and the CIM Pro Services group to complete the bulk of the customization work before you officially deploy and move into dual-management of content mode.

3rd Party ERP Connectors ($)

This applies if you are syncing data with an ERP system that is supported by the CIM Pro Services group via CIMcloud’s 3rd Party Connector service.  ERP systems that fall into this category include Sage 300, Sage 500, Sage X3, Microsoft Dynamics GP, and Microsoft Dynamics AX.

  • This requires an additional billable pro services engagement.

Net New Custom Mods ($)

This applies if you contact with the CIM Pro Services group to scope, build, and install net new custom modifications to the CIMcloud platform.

  • This requires an additional billable pro services engagement.
  • We recommend deferring all net-new custom development to a future phase (so it does not slow down and/or complication your migration project).

Impact on Lead-time

Extra work will impact your lead-time.  For more details on how, read the Migration (Classic-to-Current) Lead-Times article.

Have Questions On Extra Work?

It is important that you make really informed decisions on whether or not you include the extra work you are considering in your migration scope.  Feel free to contact us for additional details on what extra work is and how it impacts your project risk, timeline, and cost.

Was this article helpful?

Related Articles