Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


titleWhen to Cut-Over?

The impact and cost of using gmStudio in your migration effort can vary widely depending on how you use it.  

Periodically during the migration project, the team must evaluate their situation and decide to do one of two things:

1) stop improving the quality of the translation process and take the resulting .NET code forward "by hand" (i.e., Cut-Over)
2) continue improving the quality of the automated translation process to reduce the work needed to finish the job

Optimizing how much the allocation of project budget should be invested in the used for automation requires considering factors such as the following:

  • team capability,
  • cost of labor,
  • project pace/schedule,
  • transition/test plan, and
  • system size/complexity. legacy system size/complexity
  • nature and pace of legacy system changes
  • acceptable duration of the transition from cut-over to production
  • team capacity and capability to complete the transition
  • productivity gains versus costs of improved automation

There is no mathematical formula for unifying all these factors to predict the optimal investment in translation tuning, I wish there was. And, these factors are very difficult to quantify. What I can say with some certainty is that a team should Cut-Over only when they are confident that the amount of work needed to finish the job by hand fits within the time and resource available.  Said another way, a premature Cut-Over means you will run out of allocated resources before you complete the upgrade project. As long as the work required to finish the job by hand is greater than the time and resources available, the team should continue investing in improving the quality of their migration solution.  In some situations, a team may decide to suspend work on the migration for a few months, then return to it when resources and priorities allow.