iblync · Parallel run and cutover

Parallel run migration: a cutover plan that keeps the old system live until you are sure

Run the old and the new system side by side on live data, compare them, and switch only when your own go or no-go criteria are met.

  • Built and supported by Interkey An Interkey product, delivered and supported by Interkey
  • One platform for migration and continuous sync The move and the replication that follows it
  • Written quote after one meeting The price is discussed in a meeting about your systems

A parallel run keeps the old system and the new one working on the same live data for an agreed period before cutover. It turns the switch from a leap into a checked decision: you compare results, rehearse the cutover, and move only when the criteria are met. iblync keeps the two sides in sync during that period.

What a parallel run is

A parallel run is a period, agreed before it starts, in which the old system and the new one both work on the same live data. The old system stays in service and remains the reference. The new one receives every change as it happens and is checked against the old one, again and again, until the business is ready to switch.

The pattern suits a move to a new platform, a migration between different database engines and a change of replication tool. What stays live in each phase, and what the final switch can still ask of you, is set out on our zero downtime migration page.

What a parallel run proves

A parallel run is worth its effort because it answers three questions with evidence before the cutover night, not after it.

  • The data arrives complete. Record counts and agreed samples match on both sides, run after run, including the records changed during the day.
  • The new applications give the same results. Reports, balances and key transactions on the new system agree with the old one on the same data.
  • The team knows the steps of the night. The cutover has been rehearsed, each person knows their step, and the time it takes is known rather than guessed.

If any of the three is not yet true, the parallel run simply continues. Nothing has been switched, and the old system is still serving.

The timeline from first load to switch-off

Six stages, in this order. How long each one lasts is set in the assessment, for your own systems.

  1. Stage 01

    Initial load

    The existing data is copied once to the new system, with transfer speed limited so that production is not slowed.

  2. Stage 02

    Continuous sync

    From then on, every change on the old system is applied to the new one as it happens. If the new system is unavailable, changes wait in a queue and are applied when it returns.

  3. Stage 03

    Regular comparison

    Record counts and agreed samples are compared on a set schedule, and every difference is explained and closed before the next comparison.

  4. Stage 04

    Cutover rehearsal

    The whole runbook is carried out end to end, on a copy or in a quiet window, including the way back. Whatever failed is fixed and rehearsed again.

  5. Stage 05

    Go or no-go decision

    The people who decide meet and check the criteria agreed in advance. Any criterion not met means no-go, and the parallel run continues.

  6. Stage 06

    Cutover, then a monitoring period

    The runbook is carried out. The old system stays available through an agreed monitoring period, and is switched off only when the business confirms the new one.

Go or no-go: criteria to agree in advance

Eight conditions, each one measurable, written down and signed before the night. On the night they are checked one by one, not debated.

  • Record counts match on both sides for every table in scope.
  • The agreed samples match, value by value.
  • Sync lag is within the limit agreed in advance.
  • The cutover rehearsal succeeded, including the way back.
  • The fallback plan is ready: who calls it, and the steps back to the old system.
  • The people who decide are present, or reachable, for the whole window.
  • The working window is approved by the business and by every team involved.
  • One communication channel is agreed, and everyone working that night uses it.

A cutover runbook you can copy

A cutover runbook template: each step, who owns it, the evidence that it is done, and what to do if it fails
StepOwnerEvidence it is doneIf it fails
Confirm the go decisionDecision ownerThe go or no-go criteria checked and the decision recordedNo-go: the old system stays in service and the parallel run continues
Announce the start of the windowProject leadMessage sent on the agreed channel to every team and to usersHold the start and announce the new time
Stop writes on the old systemApplication ownerNo new transactions recorded on the old systemReopen writes and stop the cutover
Wait for the last change to arriveReplication teamNo change left waiting between the two systemsReopen writes on the old system and return to the parallel run
Run the final comparisonData ownerRecord counts and agreed samples matchFollow the fallback plan: the old system resumes service
Switch the connectionsInfrastructure teamApplications, integrations and reports point to the new system, each one ticked off a listPoint the connections back to the old system
Run the smoke testBusiness testersThe agreed key transactions pass on the new systemFollow the fallback plan
Open writes on the new systemApplication ownerThe first real transactions are recorded on the new systemFollow the fallback plan
Announce the resultProject leadMessage sent on the agreed channelAnnounce the return to the old system and the next date
Start the monitoring periodOperations teamThe agreed checks run on schedule, and the old system is still availableDecide on the fallback plan with the decision owner

Copy the table into your own plan and replace the roles with names. The order matters more than the wording: writes stop before the last change is awaited, and the final comparison comes before any connection moves. How to rehearse the night and what a way back means are covered in our migration checklist.

What iblync does during the parallel run

iblync, Interkey's platform for migration and continuous sync, keeps the two sides in step. It is delivered with the Interkey team that operates it.

01

Continuous real-time sync

Every change on the old system is applied to the new one as it happens, for the whole parallel run. More on our real-time replication page.

02

Control over the load

Transfer speed and resource use can be limited, so the old system keeps serving users at its normal pace while the new one is filled.

03

A queue when the target stops

If the new system is unavailable, for maintenance or a fix, changes wait in a queue and are applied when it returns.

04

Sync in both directions

Both databases accept writes, and each side's changes are applied to the other continuously. More on our bidirectional sync page.

When a parallel run is not worth it

A direct move can be enough

A parallel run costs effort: two systems to run, compare and watch. It is not always worth it. If the data is small and the business can accept a downtime window long enough to copy it once and check it, a direct move with a careful check is simpler. The same is true of a read-only system, such as an archive, where nothing changes during the move. Our migration checklist helps you decide.

Questions about parallel runs and cutover

What is a parallel run in data migration?

A parallel run is a period in which the old system and the new one both work on the same live data before cutover, while their results are compared. Its length is agreed in advance. The old system stays the reference throughout, and the switch happens only when criteria agreed beforehand are met, so the decision rests on evidence rather than on a date in the plan.

How long should a parallel run last?

Long enough to cover one full business cycle that includes your most important operations, such as a month-end close. There is no fixed number: the length depends on your own systems and processes, and it is set in the assessment. If the go or no-go criteria are not met at the end, the parallel run simply continues until they are.

What is a cutover plan?

A cutover plan is the document that sets out the steps of the cutover night in order, who carries out each step, the evidence that each one is done, and what to do if it fails. It is written before the night and rehearsed at least once. The runbook table on this page is a template you can copy into your own plan.

What are go or no-go criteria?

They are measurable conditions, agreed and written down before the cutover night, that decide whether the switch goes ahead. Typical ones are matching record counts, matching agreed samples, sync lag within the agreed limit and a successful rehearsal. On the night they are checked one by one, and the decision follows the criteria, not the mood in the room.

What happens if the new system stops during the parallel run?

The old system keeps serving as before. With iblync, changes wait in a queue while the new system is unavailable and are applied when it returns. The comparison then resumes, and every stage affected by the stop is checked again before the go or no-go decision, so the interruption is visible in the evidence rather than hidden by it.

Can iblync keep both systems in sync during the run?

Yes. iblync applies every change from the source to the target as it happens, for the whole parallel run, with transfer speed and resource use limited so production is not slowed. Where both systems must accept writes, it also supports synchronisation in both directions. Our real-time replication page explains how it works.

Next step

Plan a parallel run with us

Tell us the source system and the new one, the rough data volume, the cutover window you have in mind, and what the parallel run must prove before you decide.

Required field

By sending this form, you agree to our Privacy Notice.

What happens next

  1. We read your request
  2. An engineer contacts you
  3. You get an estimate or a demo
  • Built and supported by Interkey

    An Interkey product, delivered and supported by Interkey

  • One platform for migration and continuous sync

    The move and the replication that follows it

  • Written quote after one meeting

    The price is discussed in a meeting about your systems

Or directly

+966-11-2180999 [email protected]

Tawuniya Towers, North Tower, 7th Floor, King Fahad Highway, Olaya, P.O. Box 56835, Riyadh 11564, Saudi Arabia

or Read the migration checklist

Published by Interkey. Last updated . Interkey is registered in Riyadh, Saudi Arabia under commercial registration 1010156897.