Legacy systems & Transfer
Transfer data from a legacy application without losing existing records
A legacy dataset is not yet a ready-to-use import for the new system. In addition to files or tables, meanings, relationships and required information must be clarified. An unavailable vendor makes transfer harder, but not automatically impossible.
- SourcePreserved legacy data
- Check the connectionUnderstand & check
- DestinationPlanned destination dataset
How this appears in daily operation
Customers, products and historical orders are stored in an application whose developer is no longer reachable. The new application needs to use them. We start by taking stock: what still runs, which access methods exist and which data is really needed?
Distinguish typical causes
Only files available, without explained data
File names and table names do not yet explain how customers, orders and line items relate to one another.
No complete export path known
A visible list export may contain only part of the data. Documents, relationships or historical values may be missing.
Destination rules differ
The new system may use different required fields, identifiers or meanings. Simply copying columns is then insufficient.
What you can check first
Clarify existing data and recovery
Record existing backups, application version and responsibilities. Testing begins with a suitable copy, rather than changes to the original.
Inventory access methods
Record available exports, database type, documentation and known permissions. Permitted use of access methods is clarified with the operator.
Limit the destination and scope
Which customers, products, transactions or documents does the new system need? A small, representative selection makes the requirements tangible.
When the problem runs deeper
We check more than whether data can be read. Relationships, completeness and a traceable comparison in the destination matter just as much. A backup and a migration format can serve different purposes. PostgreSQL, for example, documents logical SQL dumps as a distinct backup method.
A trial run must allow business validation
For the agreed selection, source and destination records are compared: identifiers, counts, relationships and selected totals. The business determines which values matter. A technically successful import is not yet business approval.
Transfer or continued use?
Not every old system needs immediate replacement. Sometimes limited access is sufficient for a new store or an overview. If a system is replaced, the transition, responsibilities and handling of newly generated data are planned together.
When support makes sense
If the vendor is unavailable, the format is unknown or operations must continue in parallel, a planned transfer path helps. Start with application names, data types and the desired destination. Full customer datasets are not needed for initial contact.
The right solution pathReuse old data and plan transfersSources for technical assessment
Technical content reviewed on 7 October 2026. Vendor statements refer to the products named; they do not replace checking your specific configuration.
Clarify the next step together.
Your application names and a brief description of the problem are enough to start.