Automated app migration promises speed and efficiency, but the real challenge lies in handling a project's unique complexities. While tools like our CodeWays provide a decent automated code conversion level out of the box (up to 80%), the key to high-speed and successful migration is our ability to customize the tool's core logic.

Read on to learn how we adapt CodeWays to fit the nuances of your source code and ensure a rapid transition.

How Customization Provides Measurable Results

Automated app conversion isn't a simple text replacement. It requires a deep understanding of code structure and syntax. CodeWays analyzes the source application, modifies the rules that operate there, and handles complex migration scenarios that would otherwise require significant manual intervention.

Whenever it struggles to convert the source code with the default configurations, our app migration team steps in to adjust its features to the individual case.

1. Handling third-party components

Many legacy applications rely on third-party libraries and proprietary components that have no direct equivalent in the target language. For example, a Delphi application might use a specific component for data grids or reporting. A standard automated tool would simply fail to recognize it.

Solution

Our team writes a custom traversal rule. This rule identifies the source component, understands its properties and methods, and maps them to a corresponding modern library in the target language, such as C# or Java.

The tool will be able to automatically replace the old component with the new one, converting all associated logic and properties without human intervention.

  • Manual effort without customization: A single third-party component used in 1,000 places could require a developer to manually rewrite 1,000 lines of code. At an average of 5 minutes per line (locating the code, analyzing, replacing), this totals approximately 83 hours of manual labor.
  • Automated effort with customization: By creating one custom rule, the tool automates the process in minutes. The time is reduced to less than 1 hour for rule creation and testing, achieving a 98% reduction in effort.

2. Embedded SQL conversion

Applications with embedded SQL (ESQL) are a common migration challenge. The syntax and data types for SQL statements are often specific to the source database and must be converted for the target database.

Solution

We can create a specialized parser within CodeWays that isolates the SQL statements from the host language. Custom rules will be then applied to this parsed SQL.

For a codebase with 2,500 embedded SQL statements, a manual rewrite at 5 minutes per statement would take around 208 hours. Our customized rules can process this entire set in under an hour or even minutes, after the initial rule development.

The level of detail ensures the migrated code is not only syntactically correct but also functionally identical to the original, which reduces post-migration testing and rework.

3. Architecture transformation

Beyond language migration, CodeWays can also change the architecture of an application, for example, from a desktop client-server model to a modern web-based architecture.

Solution

We implement a set of transformation rules that restructure the code that cannot be restructured automatically. A typical manual rewrite for an application of 50,000 lines of code with an architectural change could take 6-12 months with a team of developers.

By breaking down the monolith and generating the necessary components for a new architecture, CodeWays can complete the code conversion in as little as 3 months for some projects, saving 50% or more of the project timeline.

Our custom app migration approach allows us to deliver a complete, high-quality, and modern application with unparalleled speed.

FAQs

What exactly does Ispirer customize in CodeWays?

We customize the migration rules and tool logic itself. When we customize the tool, we are essentially writing new rules that tell the migration engine how to handle specific code patterns that are not covered by the default logic.

This includes handling proprietary third-party components, non-standard syntax, or specific architectural transformations.

Why is customization necessary if the tool is already automated?

No two legacy applications are the same. While the core of a language may be standardized, decades of development often lead to unique coding conventions, reliance on outdated libraries, and idiosyncratic business logic.

Customization bridges the gap between a general-purpose automation tool and a unique, complex codebase. Without it, a significant portion of the code would require manual intervention, which is slow, prone to errors, and defeats the purpose of automation.

Our customization ensures that the automation rate remains high, even for the most challenging projects.

What is the process for customizing CodeWays for my project?

The process is highly collaborative and begins with a free assessment. We first use our Metrics tool to analyze your codebase and identify the level of complexity and any unique code features that will require custom rules.

Based on this analysis, our migration experts develop and implement the rules needed to handle your app. These rules are integrated into your licensed version of CodeWays, so you can run a highly automated and accurate conversion.

What's the benefit of customization compared to a manual rewrite?

Customization allows for a hybrid approach that combines the speed of automation with the precision of human expertise. The main benefit is a massive reduction in project time and cost.

For example, converting thousands of lines of code with a proprietary function could take weeks or months with a manual rewrite. But by creating one custom rule in CodeWays, that same conversion can be done in minutes. You can save a significant amount of labor and get the application to market faster.