Reuse legacy systems
The application is older.
The data is valuable.
Read, export or otherwise deliver data from an existing application: we investigate how your existing records can continue to be useful.
Discuss your projectThe starting point
The data exists.
So does the workaround.
The old application still serves its purpose. Its data just does not reach where it is needed today. Before replacing everything, we investigate existing exports, databases and documented interfaces.
What we clarify together
- Record existing data sources and permitted access methods
- Understand tables, relationships and data meaning
- Initially transfer data in a controlled, preferably read-only way
- Create exports in CSV, XML, JSON or a suitable destination format
- Consider ongoing operation and vendor conditions
One possible scenario
One existing database. One new use.
An internal application contains the required order data but offers no modern API. Approved read access allows selected data to be prepared and delivered for a new overview.
Illustrative example; no claim of an already delivered customer project.
For technical assessment
The technology follows
the task.
We evaluate these approaches according to your data and your systems' capabilities.
SQL databases
Use queries, views and appropriate access permissions. We check the data model, load and permissions before regularly reading production data.
ODBC and drivers
Existing ODBC access can make data available to additional applications. Drivers, versions, network and licences must fit together.
Existing exports
A periodic file export can also be the right starting point. We automate the subsequent processing and document limitations and data freshness.
Before we start
Good to know.
Your specific starting point determines the right solution path.
Can data be exported from a legacy application?
Exports, database access or vendor tools are often available. We check the specific application, data formats and your usage rights. Without knowing the system, we cannot reliably promise that export is possible.
Can you read data through ODBC?
Yes, provided a suitable driver and authorized access are available. We clarify which tables are needed and how queries can minimize their impact on ongoing operations.
Does this change the production database?
We prefer read-only access for transfers. Writing is a separate, carefully agreed step requiring suitable interfaces and business rules.
Can this also support a later migration?
A documented data transfer can prepare a migration. This additionally requires checking completeness, history, relationships and the new system's requirements.
The next consideration
Perhaps there's
more to connect.
A few brief details are enough
What would you like to do with your existing data?
Your existing application is the starting point. Tell us what you would like to keep using.
Your enquiry to Datenquelle
All five fields are required.
