The end is looming for costly old platforms and for very good reasons: The number of experts with insight into legacy systems is constantly declining. IT budgets are strained by hefty license and maintenance costs. But most of all, the company is downright cut off from technical advancement.
Legacy system modernization and the migration to new platforms are high on the list of priorities for IT divisions. But companies are finding the shift from old systems to new platforms anything but easy, regardless of the related perspectives on flexibility and simplification. By migrating the code automatically, we make legacy system modernization projects far less menacing. Thanks to our Cross-Platform Technology cpTech, an automatic migration to modern platforms such as Linux, Java, Web etc. is generally 100% possible.
Legacy systems have no future in the medium term, that much is for sure. But what suits best when? Migration, new development, standard software or outsourcing: four ways of IT modernization – graphically visualized for you.
Minimal frozen zone
Further development can continue even while the legacy system migration project is underway.
Once migrated, the target code can easily be configured and aligned in accordance with the customer’s style guide.
Serviceable source code
The migrated source code is fully serviceable, thus nothing stands in the way of further development.
The PASS Migration Factory aims to transform your legacy systems into target platforms of your choice. But this legacy system migration to a modern environment signals more than just a change from old to new. It also provides unique opportunities to achieve a range of key objectives bringing with them positive effects for the entire IT shop. The results are sure to convince you:
Shifting to new platforms has allowed us to slash operating costs by over 70%. Maintenance and licensing costs also have decreased since the legacy system migration to the new platform.
The transformation to new technologies prepares your infrastructure for the challenges of digital business models and helps you devise your future strategy on the web.
By supporting current industry standards, our migration method allows you to choose between commercial and open source products. Furthermore it guarantees access to an extensive expert know-how.
USERS AND THE TECHNICAL TEAM
- Quality gains thanks to higher performance (process optimization) and state-of-the-art technologies (GUI etc.)
- Efficiency boost (particularly in product development) due to a shorter time-to-market
IT MANAGERS AND DEPARTMENT HEADS
- Reduced maintenance required
- Focus on optimization
- Flexibility: business requirements implemented more swiftly
- Quality boost due to higher process security
DECISION-MAKERS OR MANAGEMENT
- Cost reduction (maintenance, investment and operation)
- Increased efficiency thanks to a shorter time-to-market
- Flexibility for your IT strategy
An exemplary legacy system migration scenario
We specialize in automated migration technologies. In the course of numerous legacy system modernization projects we developed our Cross-Platform Technology (cpTech), making the switch to new and cost-efficient platforms possible. We calibrate our migration robots to meet project-specific requirements, generally allowing us to reach automation ratios up to 100%. The project unfolds in two phases:
Phase 1: Proof of Concept
Safeguarding your investment
- Verify the feasibility of the desired migration
- Confirm the reliability of the procedure in short time
- Set out the entire expense and timeline of the project in detail
As part of the proof of concept (feasibility study), a prototype legacy system migration is performed in order to gain a representative outline of the applications. Even at this early stage, we employ all steps of the Migration Factory process, including the initial calibration of the migration robots to the project requirements.
- Evolutionary prototype
- Definition of the target architecture (hardware, operating system, programming language, and more)
- Mappings on architectural, design and command levels
- Specification of interfaces and dependencies
- Expected degree of automation (> 95%)
- Possible project risks
- Extract of the transformed code for review
Phase 2: Migration Project
Automated legacy system migration in three steps
The migration processes defined in the feasibility study are applied to the overall code base. If you opted for a language migration in addition to a purely architectural migration, the project is implemented in three fully automated stages:
Some people are skeptical when it comes to a fully automated migration. Indeed special cases do exist, where transformation without manual intervention is not possible. But we have developed a solution for these cases based on intelligent adaptation of the production line.
Many successful legacy system modernization projects prove that our Migration Factory is based on a sophisticated concept, in both technological and organizational terms:
- It is the outcome of more than 30 years of IT projects.
- It boasts an unrivaled degree of automation.
- The configuration is adapted to each individual project situation.
- Automation guarantees security and risk minimization.
- The Migration Factory is cost-effective, error-free and flexible.
Let us prove the efficiency of our strategy to you!
By the way: we credit the costs of a preliminary proof of concept for your legacy system modernization project to the project costs, should you afterwards decide to commission the migration.
Yes! We calibrate the migration robots in the course of the migration project. During this phase, new code can be delivered at any time. The code-freeze timing can be scheduled close to the end of the legacy system modernization project. It is limited to the automatic migration phase, namely from the time the start button is clicked, right up to the output.
Yes. In fact, it will often outperform it, because the new platform is more efficient (less memory used, resulting in faster lead times). Comparable performance is attained when migrating a monolithic legacy application to a new target platform, through caching/refactoring, reconfiguring of data accesses, asynchronous accesses etc.
The source code we generate is adapted to the style guide of our customers and therefore considered easy to maintain. As part of a hybrid strategy – the first part of which involves porting the solution to a new platform, followed by new developments directly on the target platform – patterns of an e.g. structured programming language are ported onto an object-oriented programming language. Occasionally, conclusions about the original language can be drawn, but customers do not consider this as impeding the maintenance load.