Getting Started

Connect your databases and run your first migration in under 5 minutes.

Quickstart: Migrate MongoDB to PostgreSQL

NoSQLSync connects to your MongoDB source, auto-detects collections and schema, and migrates data to your SQL target in three steps.

Step 1 — Add a source connection

Navigate to Dashboard → Connections → Add Connection. Select Source and MongoDB. Paste your MongoDB Atlas URI:

mongodb+srv://user:[email protected]/?retryWrites=true

Click Test Connection to verify, then save. Credentials are encrypted with AES-256-GCM and used only during the migration job.

Step 2 — Add a target connection

Add a second connection as Target. Supported SQL targets:

  • PostgreSQL (12–17, RDS, Aurora, Cloud SQL, Supabase)
  • MySQL (5.7, 8.0, RDS, Cloud SQL, PlanetScale)
  • BigQuery (Storage Write API)
  • Snowflake (VARIANT + structured, Snowpipe)
  • Amazon Redshift, ClickHouse, SQL Server, MariaDB

For PostgreSQL/MySQL, provide a URI. For BigQuery, provide Project ID + Dataset ID + Service Account JSON. For Snowflake, provide Account, Username, Password, Warehouse, Database, and Schema.

Step 3 — Create your first migration

Click New Migration from the sidebar. The 5-step wizard walks you through:

  • Name your migration, pick source connection + database + collection
  • Pick target connection + table name and mode (One-time or Live CDC)
  • Review auto-detected schema — adjust types, rename columns, flatten nested docs
  • Set schedule (one-time or recurring)
  • Review summary and launch

Connection credentials by database type

TypeWhat you need
MongoDBConnection URI
PostgreSQL / MySQLConnection URI
BigQueryProject ID, Dataset ID, Service Account JSON
SnowflakeAccount, Username, Password, Warehouse, DB, Schema
DynamoDBRegion, Access Key ID, Secret Access Key
FirestoreService Account JSON
ClickHouseHost URL, Database, Username, Password
SQL ServerServer, Port, Database, Username, Password
MariaDBConnection URI

Migration modes

ModeDescriptionUse case
One-timeBulk copies all matching documents, then completesSnapshot migration
Live CDCBulk load + continuous oplog tailing for real-time syncZero-downtime cutover

What happens when you launch?

The migration enters queued status, then running. Progress is tracked in real time — you can watch record counts update and view live logs. One-time jobs have 3 automatic retries on failure. CDC jobs have 5 retries with exponential back-off.