Cobol to Java transformation projects take weeks instead of years

• The short completion time of the LeTS automated process means you can have your transformed system up and running months if not years ahead of your competition.
• Converting systems by hand is both expensive and unfeasable. Even a one million line system can take months or even years to convert by hand. Long before your system is completely hand converted it will be technologically obsolete.
• Automated transformation cuts costs by allowing expensive human resources to concentrate on more productive design, testing, and implementation tasks instead of less productive and repetitive tasks.

The automated transformation process is relatively insensitive to the size of a transformation project

• Using the LeTS automated process a ten million line transformation project can be completed in only a little more time than a one million line project.
• Economies of scale can be realized by transforming large amounts of legacy code in a single transformation project.

The cost of an automated transformation project can be determined before the project begins

• Because the transformation process is automated cost determination is also automated.
• The basic transformation cost is based on a fee per line of legacy source code processed. Multiplying the fee by the number of lines of legacy source code to be processed sets the basic project cost before it begins.
• The only way the basic cost of a project can change after it has begun is if you add additional lines of legacy source code to the project after it has begun. And even then you will know the additional cost by multiplying the number of additional lines by the per line fee.