Introduction to Relational Migrator

Map and Model Data

Relational Migrator provides an entity-relationship diagram builder to map your relational schema to a MongoDB schema. You can start with a recommended schema, a 1:1 mapping, or create a new schema from scratch. For more information, see Data Modeling.

Generate Application Code

Relational Migrator generates MongoDB-compatible C#, Java, and JavaScript application code for entity classes, persistence layers, and APIs.

Code generation templates support JSON output and common application frameworks like Spring Data, Node, and Mongoose. For more information, see Code Generation Templates.

Convert and Validate SQL Objects

Relational Migrator uses generative AI to convert SQL queries, views, and stored procedures into MongoDB-compatible code for C#, Java, or JavaScript.

You can test queries within Relational Migrator to validate converted SQL and ensure that your queries are compatible with MongoDB.

Migrate to MongoDB

Use Relational Migrator to migrate data from supported relational databases to MongoDB Atlas or a self-managed MongoDB deployment. You can choose either a snapshot migration, or continuous synchronization with Change Data Capture (CDC). For more information, see Use Cases.

Relational Migrator integrates with Apache Kafka and Confluent Cloud for large scale migrations. For more information, see Kafka Deployment Guide.

Migrate During Scheduled Downtime

If your application does not require constant uptime, such as in the case of an internal application, you can have the migration occur during scheduled downtime. Migrating during downtime is the easiest way to configure and complete the migration process.

When you start the migration process, Relational Migrator takes a snapshot of the data on the legacy application and migrates the data from that point in time. During the migration process, your legacy application can remain online to support incoming reads, but cannot support incoming writes. The length of the migration process depends on several factors, such as the amount of data being migrated and your connection speed.

After the migration completes, take your legacy application offline and launch your new application.

Migrate Without Downtime

If your application must remain online to support reads and writes during the migration process, you can use Change Data Capture (CDC) to migrate data without downtime. This process is called a continuous migration.

When you start a continuous migration job, Relational Migrator takes a snapshot of the data on the legacy application and tracks database updates in near real time. During the migration process, your source and destination databases remain in sync.

After the continuous migration job completes, you can transfer users to the new application and shut down the legacy application.

To learn more about migration jobs, see Data Migration.

Unsupported Scenarios

Relational Migrator currently does not support migrating an operational data store. Depending on your workload, migrating a data store could cause CDC to run indefinitely without completing, which is not recommended with Relational Migrator.

Relational Migrator will support more migration scenarios and use cases in future releases.

Source Databases and Versions

Relational Migrator supports the following source databases:

Target Databases and Versions

Relational Migrator supports the following target databases: