Migrate without a long outage
Move data to the new system once or in phases while the old one keeps working. See zero downtime migration with iblync.
iblync · Connectors
Published connectors for relational databases, NoSQL, search and graph stores, Apache Spark and object storage, and custom connectors built when your system is not listed.
iblync connects relational databases such as Oracle, MySQL, PostgreSQL, SQL Server and IBM Db2, NoSQL, search and graph stores such as MongoDB, Couchbase, Cassandra, Redis, Elasticsearch and Neo4j, Apache Spark, and Amazon S3 object storage. When a source or target is not listed, Interkey builds a custom connector as part of the project. Each pair is confirmed in the assessment before a quote.
| System | Type | Read the guide |
|---|---|---|
| Oracle | Relational database | Oracle migration |
| SQL Server | Relational database | SQL Server migration |
| MySQL | Relational database | MySQL replication |
| PostgreSQL | Relational database | PostgreSQL migration |
| IBM Db2 | Relational database, on LUW, z/OS and IBM i | Guide not yet published |
| MongoDB | Document database | Guide not yet published |
| Couchbase | Document database | Couchbase with Interkey |
| Cassandra | Wide-column database | Guide not yet published |
| Redis | Key-value store | Guide not yet published |
| Elasticsearch | Search engine | Guide not yet published |
| Neo4j | Graph database | Guide not yet published |
| Apache Spark | Data processing engine | Guide not yet published |
| Amazon S3 | Object storage | Object storage migration |
Apache Kafka works as the bridge between systems, not as a source or a target.
The table lists the connectors we publish. iblync also connects to systems that are not named here, and the list grows as projects need it. If your source or target is missing, do not read that as a no: send us its name and version with the form at the end of this page, and we will tell you whether a connector exists for it today or has to be built.
Interkey builds a custom connector when a project needs one, as part of that project rather than as a separate product. An unsupported system is then a connector to build, not a reason the migration or the sync cannot go ahead.
To estimate the work, we need three things from you: the interface documentation of the system (how data is read from it and written to it), access to a test environment where the connector can be built and checked without touching production, and a sample of the data it holds. With those, the connector is scoped with the rest of the project, and it is covered in the same written quote after the meeting.
The names and versions of the systems, the direction you need, and a rough data volume, through the form on this page.
Our engineers go through each pair with your team: versions, permissions, where iblync runs and how it reaches both sides.
Each pair confirmed or marked as a custom connector to build, with the plan for the work and a written quote after the meeting.
Move data to the new system once or in phases while the old one keeps working. See zero downtime migration with iblync.
Continuous real-time replication from the source to the target, with transfer speed you control. See real time replication.
Both systems accept writes and each side's changes reach the other. See bidirectional sync.
A name on the list means iblync connects to that system
It does not say whether the system works as a source, a target or both in your project, or which versions apply. The direction and the version are confirmed for each pair in the assessment.
Two short recordings from the iblync product channel: a move into Couchbase, and a move into Amazon S3 and S3-compatible storage.
Data migration from SQL Server to CouchbaseVideo on YouTube, 3:19
Data migration from SQL Server to Amazon S3 and S3-compatible storageVideo on YouTube, 2:51RelatedData migration from SQL Server to CouchbaseVideo on YouTube, 3:19Data migration from SQL Server to Amazon S3 and S3-compatible storageVideo on YouTube, 2:51
iblync connects to Oracle, SQL Server, MySQL, PostgreSQL, IBM Db2 (on LUW, z/OS and IBM i), MongoDB, Couchbase, Cassandra, Redis, Elasticsearch and Neo4j, as well as Apache Spark and Amazon S3. It also connects to other systems on request, and Interkey builds custom connectors where a project needs them.
Yes, through a custom connector that Interkey builds as part of the project. To scope it we need the system's interface documentation and a test environment. The connector is discussed in the same meeting as the rest of the project and included in the written quote that follows.
Not necessarily. A name on the list means iblync connects to that system; whether it acts as a source, a target or both in your project is confirmed for each pair in the assessment, together with the versions on both sides.
iblync connects to the engines on this list wherever they run, in your data centre or in the cloud. What is checked in the assessment is whether iblync can reach both systems from where it runs for your project, and where it runs is decided per project.
Next
Next step
Tell us the source and target systems with their versions, the direction you need and a rough data volume. We will confirm each pair, or tell you which connector has to be built.
What happens next
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