Home ServicesSoftware Modernization & Migration

Software Modernization & Migration

Visual FoxPro, Visual Basic, Access: systems that support your business but no longer have anyone maintaining them. The same applies to established client-server applications. We replace them while preserving their business logic. The time required depends on what is already there, ranging from a few months to over a year. Our separate site, foxpro.de, covers FoxPro replacements in detail.

Assessment before the proposal

We read the legacy source code and explain what we find: missing normalisation, calculations in UI events, passwords in code or writes to system folders. Both sides then understand the starting point.

More than a one-to-one rebuild

Source code shows what happens, but rarely why. We decide what to retain with your key users. When a workflow takes a detour, we first ask why: some are old workarounds, while others are the real business process.

Transfer the complete dataset

With every deployment to the test environment, we migrate the entire dataset again and compare the result with the legacy system. No script runs for the first time on cutover day. If stored values differ from what would be calculated today, we agree with you beforehand whether to use the stored or recalculated value.

A rollback is part of the plan

We plan the cutover window together and rehearse it in staging. If the smoke tests fail, we stop the cutover and your legacy system keeps running.

Analyse data without replacing the system

Sometimes replacement is not the first question. If figures are trapped in a legacy system, our data pump extracts them for analysis. Access is read-only, usually at night, and the legacy system stays unchanged. Daytime users notice no difference. We agree how current the figures need to be and what you want to know about changes. All existing data is included, but tracking who changed what and when can only begin with the first run. This is often the quickest step, and for several years it may be the only one needed.

Preserve knowledge

We provide documentation and training using a train-the-trainer approach: your key users can then train their colleagues. Otherwise, replacement simply creates the next black box.

Replacing is not the only answer

Before we talk about a replacement, we establish whether your legacy system has to go at all.

„The system runs, but we cannot get at our figures.“

The routeKeep running it and report on it

Our data pump, HydraData, extracts the data and makes it available in a modern database. Access to the legacy system is read-only and usually takes place outside working hours. The work is limited to setting up the connection and agreeing two things in advance: how current the figures need to be, and what you want to know about changes.

Fits when: If day-to-day work with the legacy system is fine and only the reporting is missing, this is often the quickest step and for some years the only one needed.

„What we want to do next cannot be built in this system any more.“

The routeReplace it fully

We read the source code, speak to your key users and decide together which functions belong in the new system. Depending on the existing system, this can take from a few months to over a year. Your main contribution is your key users’ time: they usually review a working version every two weeks.

Fits when: This applies when requirements keep being deferred because the legacy system cannot support them. Often, a previous replacement attempt has already failed.

„We manage leasing or finance contracts in a fat client.“

The routeMove to vertragWerk

vertragWerk is our own web-based solution for contract management, calculation and point of sale, developed from our work on eLeaseWorld and M-ASSET. The software is in beta. We demonstrate the available features and assess together how they fit your requirements.

Fits when: This route is worth considering if your domain is that of a leasing or finance system and you do not need a fixed date for the changeover.

You decide which approach to take, based on our assessment of the source code and discussions with your key users about how well the existing system still meets your needs. We explain beforehand whether that analysis is a separate service or part of preparing a proposal.

These projects led us to build HydraData, a data pump that transfers data from DBF/DBC and Access applications to modern databases, as a foundation for migration or analysis. We made it open source because a migration tool the customer cannot inspect would be part of the problem.

Understand your situation. Agree the next steps together.

Tell us what works today and what you would like to change. The first conversation is free and without obligation; afterwards, you receive an initial assessment or possible next steps. You incur costs only when you accept a proposal. For a more detailed business and technical assessment, we agree a separate engagement in advance, with a clear scope and limits on time and cost.

Discuss your project