Page tree

Versions Compared


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


Ball Park Upgrade Service Pricing

Estimated Level Of Effort by System Size and Scope*


Image Modified

Option 1: Build Complete Upgrade

.NET code with all Build issues resolved;
(external COM references replaced with .NET stub assemblies) 

Option 2: Custom Reengineered Upgrade

.NET code with all Build issues resolved, and
custom Reengineering features implemented.

Most of the effoert is in defining, designing, and implementing
custom re-engineering features.

Option 3: Custom Functional Upgrade

.NET code with Build issues resolved, and custom
Reengineering and Runtime
features implemented and tested.

Most of the effort is in defining and executing test cases.

* Contact Great Migrations to discuss The effort model shown in the chart above makes many assumptions about the complexity of the code and the efficiency of the team performing the work.  Furthermore, the total price of a project depends on many other factors such as the cost of labor for different resources and the desired schedule of the project.  Contact Great Migrations to learn more about the estimating model behind this chart and discuss developing one that fits your specific situation.

"Project Size"

The concept of "Project Size" as used in the service pricing model is somewhat subjective but it correlates with the metrics of the system being upgraded (numbers of VBP/ASP units, numbers of files, LOC) and the complexity of the upgrade requirements. 


The Huge category is simply defined as larger than "Large"; up to 2-3 times "larger".  In some situations, you might have a system or a portfolio of systems that is 4-10+ times larger than "Large".  gmStudio is an industrial-strength tool that can help you "cash in" the enormous investment embodied in such these colossal systems; it has the features and performance needed to be successful in the largest upgrade efforts.  The value proposition of using gmStudio and the Tool-Assisted Rewrite methodology is most dramatic on large-scale systems, where performance and economies of scale make the difference.  A couple of success stories in this category include: