|
| 1 | +.. _relational-migrator-get-started: |
| 2 | + |
| 3 | +==================================== |
| 4 | +Get Started with Relational Migrator |
| 5 | +==================================== |
| 6 | + |
| 7 | +.. facet:: |
| 8 | + :name: genre |
| 9 | + :values: tutorial |
| 10 | + |
| 11 | +.. meta:: |
| 12 | + :description: MongoDB Relational Migrator is a tool to help you migrate your relational workloads to MongoDB. |
| 13 | + :keywords: database migration, database conversion |
| 14 | + |
| 15 | +.. contents:: On this page |
| 16 | + :local: |
| 17 | + :backlinks: none |
| 18 | + :depth: 1 |
| 19 | + :class: singlecol |
| 20 | + |
| 21 | +Relational Migrator is a tool to help you migrate your relational |
| 22 | +data to MongoDB. This page guides you through installing the tool |
| 23 | +and running your first sync job. |
| 24 | + |
| 25 | +To get familiar with Relational Migrator capabilities, |
| 26 | +features, and use cases, review the following resources: |
| 27 | + |
| 28 | +- :ref:`<supported-databases>` |
| 29 | +- :ref:`<rm-migration-scenarios>` |
| 30 | +- `Relational Migrator Learning Byte <https://learn.mongodb.com/courses/mongodb-relational-migrator>`__ |
| 31 | + |
| 32 | +Steps |
| 33 | +----- |
| 34 | + |
| 35 | +.. procedure:: |
| 36 | + |
| 37 | + .. step:: Install |
| 38 | + |
| 39 | + You can install Relational Migrator with a |
| 40 | + :ref:`single machine install <single-machine-install>` suitable |
| 41 | + for testing or a :ref:`unattended server install <unattended-server>` |
| 42 | + for production workloads. |
| 43 | + |
| 44 | + .. step:: Create a project |
| 45 | + |
| 46 | + To start using Relational Migrator, |
| 47 | + :ref:`create a project <rm-projects>`. Projects hold the |
| 48 | + settings, schema conversion logic, and table mappings for a |
| 49 | + migration. You can connect your |
| 50 | + source and destination databases with the appropriate |
| 51 | + :ref:`connection strings <rm-connection-strings>`. |
| 52 | + |
| 53 | + .. step:: Create mapping rules with suggested mappings |
| 54 | + |
| 55 | + Use :ref:`suggested mappings<rm-new-rules-from-mappings>` to |
| 56 | + create initial mapping rules based on your |
| 57 | + relational schema. Mapping rules specify how data from each |
| 58 | + relational table migrates to MongoDB and how columns map to |
| 59 | + fields in MongoDB documents. |
| 60 | + |
| 61 | + .. step:: Customize your mapping rules |
| 62 | + |
| 63 | + Add or update :ref:`mapping rules <rm-mapping-rules>` to create |
| 64 | + the destination data model that best matches your |
| 65 | + application needs. |
| 66 | + |
| 67 | + .. step:: Create a sync job |
| 68 | + |
| 69 | + :ref:`Sync jobs <rm-sync-jobs>` move the data from relational |
| 70 | + tables to MongoDB collections. Sync jobs have two types: |
| 71 | + |
| 72 | + - **Snapshot** for point in time migrations. |
| 73 | + - **Continuous** for ongoing change data capture zero-downtime migrations. |
| 74 | + |
| 75 | + To start your migration to MongoDB, |
| 76 | + :ref:`create a sync job <rm-create-jobs>`. |
| 77 | + |
| 78 | +.. toctree:: |
| 79 | + :titlesonly: |
| 80 | + :hidden: |
| 81 | + |
| 82 | + /getting-started/supported-databases |
| 83 | + /getting-started/migration-scenarios |
0 commit comments