Survey
What is moving, what it depends on, where the data lives, which exchanges will be affected.
The outcome is decided by preparation. The move itself lasts a few hours, while getting ready for it takes weeks.
What is moving, what it depends on, where the data lives, which exchanges will be affected.
A sequence of steps with duration estimates and points where the decision to continue is made.
A full move onto a test environment with timings and a hunt for bottlenecks.
With integrity checks and data conversion wherever the structures differ.
Actions described in advance in case a serious problem surfaces after the cutover.
We count totals and row numbers and manually spot-check the most important items.
Preparation takes two weeks and up; the move itself usually fits into a weekend.
Data volume, dependencies, exchanges, the acceptable length of the outage.
A full run on a copy against a stopwatch. The first rehearsal almost always uncovers surprises.
We do it inside the agreed window strictly to the rehearsed scenario, staying in touch from beginning to end.
For a week we watch how it behaves, and the old system stays available for reconciliation.
The old system must not be switched off straight after the move. Let it stay running for at least thirty days: something that did not travel across, or travelled in distorted form, almost always surfaces, and there will be nowhere to take it from once the system is dark.
The exact figure comes from a rehearsal, because it measures the time on your real volume. In our experience databases of up to a few hundred gigabytes move in a matter of hours, and it is better done at a weekend.
For some systems yes, through continuous synchronisation followed by a cutover. That option is dearer and harder, and it is justified where downtime genuinely cannot be allowed. Most companies find a weekend window enough.
That is exactly why a copy is taken before the start and a reconciliation is done afterwards. Nobody touches the archive until confirmation comes from your side that everything works correctly. A point of return exists at every stage.
Write what moves where and how much downtime is acceptable. We will start with a rehearsal on a copy.
Request received
It is already with a manager. You will get an answer within the working day, and urgent requests go to the duty engineer immediately.
There is no such city in the list. Check the spelling.