Survey
What we are moving, which dependencies exist, where the data is, which integrations are affected.
The success of a migration is decided by the preparation. The transfer itself is a few hours that take weeks to get ready for.
What we are moving, which dependencies exist, where the data is, which integrations are affected.
A sequence of steps with an estimate of the time for each and decision points.
A full transfer to a test landscape with timing measurement and a search for problems.
With integrity checks and conversion wherever the structure differs.
What we do if a critical problem is found after the switch.
Checksums, record counts, selective verification of key data.
Preparation takes two weeks upwards. The transfer itself usually fits into a weekend.
Volume of data, dependencies, integrations, downtime requirements.
A full run on a copy with timing measurement. The first run usually reveals several problems.
In the agreed window, following the rehearsed plan, with constant communication.
Observation during the first week, with the old system left available for reconciliation.
The old system must not be switched off immediately after the transfer. Keep it operational for at least a month: something that did not transfer or transferred incorrectly almost always turns up, and there is nowhere to take it from once the system is shut down.
Only a trial run gives the exact answer: it shows the real transfer time on your volume of data. In our experience, for databases up to a few hundred gigabytes it starts at a few hours, and a weekend is the better time to do it.
For some systems yes, through replication with a subsequent switch. It is more expensive and more complex, and it is justified where downtime really is unacceptable. For most companies a weekend window is a reasonable compromise.
That is what the copy made beforehand and the reconciliation afterwards are for. The copy stays untouched until you confirm that the new system works correctly. We do the transfer, but there is always a point to roll back to.
Tell us what we are moving and where to, and how much downtime is acceptable. We start with a trial run on a copy.
Request received
We can already see it. We will reply within one business day, and for urgent matters we will bring in the on-duty engineer right away.
City not found. Please check the spelling.