iblync · Switching tools

Switching data replication tools: move to a new platform while replication keeps running

Replace your current replication tool in stages: list what it copies today, run iblync beside it, compare the results, then switch the old one off.

  • 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
The iblync dashboard: a replication task between two databases
The iblync dashboard, from the recorded product demo.

Switching data replication tools is a short project, not a swap. You list what the current tool copies, map the same tables in the new platform, run both side by side on an agreed scope, compare the results, and only then retire the old tool. iblync, built by Interkey, is delivered with the team that runs this switch with you.

Why teams change their replication tool

Four reasons come up most often. If you are still choosing a platform, start with the nine criteria for comparing data replication tools.

01

The licence renewal is near

The renewal date is a natural point to ask whether the tool still fits the systems you run today. Ask it before you sign for another term, not after.

02

A new target the tool does not support

A new database or a cloud storage target arrives, and the current tool cannot write to it, or only with a second tool beside it.

03

Local support

When a replication job stops in production, the team needs a clear answer in its own language, from someone who knows its environment.

04

The person who ran it has left

Many tools depend on one engineer or one contractor who knew how they were set up. When that person leaves, the jobs run until the first change nobody knows how to make.

Inventory before you switch

What to inventory in the current replication tool before switching, and why each item matters
What you inventoryWhy
Sources and targetsEvery system the tool reads from or writes to, with its version, so you can confirm iblync connects to it or a connector is built for it. The current list is on the iblync connectors page.
TablesThe tables and columns copied today. They are the scope of the mapping now and of the comparison later.
Transformation rulesWhat the tool changes in the data on the way: filters, renamed columns, converted types. Each one has to be rebuilt as it is.
SchedulesWhen each job runs, and which run continuously and which on a schedule, so the time data arrives does not change.
AlertsWho is told when a job stops or falls behind, and how, so no alert is lost in the switch.
Who depends on the outputThe reports, applications and teams that read from the targets. They sign off the result before the old tool is switched off.

Keep the inventory in one table that your team and the Interkey team agree on. It is the basis of the mapping in iblync and of the comparison at the end of the parallel run.

The switch in five steps

  1. Inventory.

    We record with you what the current tool copies, item by item from the table above. What we need from you: access to the current tool's settings, and someone who knows how it works.

  2. Map in iblync.

    The Interkey team configures the same tables and the same transformation rules as low-code workflows. What we need from you: a review of the mapping, and your approval.

  3. Run both tools.

    The two tools run side by side on an agreed scope, with the load on the source limited. What we need from you: the scope, and the load you accept on production.

  4. Compare.

    The outputs of the two tools are compared table by table, and iblync's weekly and monthly replication reports help show the match. What we need from you: the acceptance checks, and sign-off from those who depend on the output.

  5. Switch the old tool off.

    The targets move to iblync, then the old tool is retired. What we need from you: the decision to switch, and its date.

Go or no-go for the switch

Six conditions, each checked and recorded before the old tool is switched off. The parallel run and cutover plan sets out how to measure them.

  • Row counts match between the old and the new output for every table in scope.
  • A sample of records matches column by column, including Arabic text, dates and numeric precision.
  • The new platform has kept pace with changes in the source for the whole agreed parallel run.
  • The load on the source stayed within the limit agreed before the run.
  • Everyone on the inventory who depends on the output has read from the new target and signed off.
  • The way back is written down: who returns to the old tool, and how, while it is still running.

What iblync does during the switch

01

Continuous real-time sync

After the initial copy, iblync carries each change as it happens, so the new target keeps pace with the source throughout the parallel run.

02

Control over transfer speed

Transfer speed and resource use can be limited, so running two tools against the same source does not slow production.

03

A queue when the target stops

If the target is unavailable, changes wait in a queue and are applied when it returns.

What changes for your team

A switch changes the daily routine, not only the software. Three questions show the difference. With your current tool:

  • Who runs it: whoever operates it today, often your own engineers or a contractor.
  • Who supports it: the vendor's support arrangements, as set in your current contract.
  • How a new source is added: your team configures it, or waits for the one person who knows the tool.

Pricing for the switch is discussed in a pricing meeting, followed by a written quote.

What a switch does not fix

The limits of a switch

Changing the tool changes how data is copied, not what the data is. Records that are duplicated, incomplete or inconsistent in the source arrive in the new target the same way, so cleaning them is a separate piece of work. And code or reports that rely on a habit of the old tool, such as the order it writes in or how it names columns, have to be found during the inventory and adjusted.

Questions about switching replication tools

Can we change our replication tool without stopping replication?

Yes. The old tool keeps replicating while iblync runs beside it on an agreed scope, with the load on the source limited. Only when the outputs of the two match, and the people who depend on them have signed off, do the targets move to iblync and the old tool is switched off. The parallel run and cutover plan covers the detail.

How long does it take to switch replication tools?

It depends on the number of sources and targets, and on how many transformation rules the current tool applies. A switch with one source and a few tables is a different project from one that spans many systems. The inventory in the first step gives you a timeline written for your own estate, before any work on the new platform starts.

What do you need from us to plan the switch?

A list of the sources, targets and tables the current tool handles today, and the date your current licence ends, if there is one. Access to the current tool's settings, and someone who knows how it was set up, makes the inventory faster. Whatever is missing is worked out together in the first step.

Will our existing targets still receive data during the switch?

Yes. Your targets keep receiving data from the old tool right up to the moment of the switch, and from iblync after it. During the parallel run the outputs of the two tools are compared without changing what your reports and applications read today, so the business carries on as before until the decision is made.

Who runs the new platform after the switch?

The Interkey team that operates iblync, working with your team. iblync is delivered with that team, so the jobs are configured, watched and supported by Interkey, and no development team is needed on your side. Support is given in Arabic and English, and your team keeps the decisions about what moves and when.

Next step

Plan the switch from your current tool

Tell us what your current tool copies today: the sources, targets and tables, and when its licence ends. The price is discussed in a meeting, followed by a written quote.

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 Plan the parallel run

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