Service
Data migration from the legacy system
We take over existing data into netPension® – including data that was considered impossible to migrate. The transition from the legacy system is seamless, without your organisation having to enter anything twice.
Why us
We have never yet handed back a migration problem unsolved – not even where another company had previously given up.
Old data is rarely clean. Some databases have grown over decades, are kept redundantly and are partly no longer traceable. No tool helps here – the only way is to work through it, field by field, rule by rule, together with the people who know the data.
Source systems
What we migrate from.
Migration is carried out from a wide variety of databases – a clean export is not a prerequisite.
Microsoft SQL Server
MySQL
Microsoft Access
Text files
and others
Our procedure
Our own automated migration process.
We have our own data migration process, which is already used during development: your production data is migrated repeatedly, and customising is carried out using this data – not test data.
At the time of implementation, the same process – now automated – runs with the current production data. The cut-over date is therefore a run that everyone involved already knows.
Process
How an implementation of netPension works.
01
Data analysis
We look at your data before we talk about effort and dates. This shows what can be taken over directly, what needs to be cleaned up and where rules are missing.
02
Mapping the business logic
Contribution and benefit histories must deliver the same results after migration as before. For this, your statutes are mapped in the calculation components and checked against the legacy data.
03
Repeated trial migration
The data is not taken over once, but again and again, and calculated against the legacy system – customising is based on your real data. Discrepancies are clarified individually, not tolerated across the board.
04
Changeover
The takeover into live operation takes place on an agreed cut-over date. After that, you continue working in the new system with the data you know.
Frequently asked questions
Questions about migration.
What happens to contribution and benefit histories?
They are taken over too. A migration that only takes the master data is not a migration – histories are the basis for every future calculation and for all evidence provided to members and the supervisory authority.
What if our legacy system does not have a clean interface?
That is the normal case. We work with what is there – database extracts, exports, in individual cases with reconstructed structures. This is exactly where migrations failed that we subsequently took over.
How long does operation stand still?
The changeover takes place on an agreed cut-over date, typically over a weekend or at the turn of the month, so that no monthly run falls in the middle. The exact framework results from the data analysis.
Would you like to see how this would look for you?
We show you netPension® along the lines of your questions – no slides, but the running software. Give us a call or request a demo.