The ScaleGrid Console Developer Hub

Welcome to the ScaleGrid Console developer hub. You'll find comprehensive guides and documentation to help you start working with ScaleGrid Console as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Import MongoDB Data From a Remote Server

See how easy it is to import your MongoDB data into your new MongoDB clusters at ScaleGrid.

Ready to upgrade to fully managed MongoDB hosting? Easily migrate your MongoDB deployments to ScaleGrid and we'll take those time-consuming management tasks off your plate so you can get back to product.

MongoDB Import Prerequisites

Here are the things you'll need to import your MongoDB data to ScaleGrid:

  • Your remote server name, port and SSL config.
  • Name(s) of databases you wish to import.
  • A username, password and authentication DB to access your remote server.
  • Your current MongoDB version update to one of the three most recent versions.

Two Methods For Importing Your MongoDB Data

  1. Import into a newly created cluster at ScaleGrid.
  2. Import during the cluster creation process.

In this tutorial, we're going to show you how to import into an existing, newly created cluster at ScaleGrid. To learn how to import your MongoDB data during the cluster creation process, check out these docs based on your plan:

Importing Into An Existing MongoDB Cluster

Before starting your import into your newly created MongoDB cluster at ScaleGrid, verify that there is no data in this cluster so that any existing data isn't overwritten. If you'd like to override your existing data in the import, first create a backup to ensure your existing data is preserved.

  1. Log into your ScaleGrid account, or start a free 30-day trial.
  2. Go to your MongoDB dashboard, and select the cluster you'd like to import to.
  3. Under the Overview tab, click Import Data.
Find your Import Data button on your MongoDB cluster details page.

Find your Import Data button on your MongoDB cluster details page.

  1. Stay on the Remote Server tab, and enter your server name and port.
  2. Select whether you want to import a single database, or all the databases (Admin and local databases will not be imported) from the remote server.
  3. If you selected to import a single database, enter your Database name and the database which user credentials must be authenticated against (Authentication DB).
  4. Next, enter the username and password for your remote server. The user must have 'read access' to the databases you are looking to import.
  5. Check the 'Yes' box if the remote server has SSL enabled.
  6. Review the information entered is correct, and click 'Import'.
  7. We will test the connectivity to the remote server once you click Import. If we are able to connect to the remote server, the import job will begin.

Your MongoDB import has now begun!

Your data will be migrated as soon as the import job is complete, and the time will vary based on the size of your data.

Configure Your New MongoDB Cluster

While your new MongoDB cluster is being created, check off these important steps to fully complete your setup process:

Grab Your MongoDB Cluster Credentials

Here are the steps to connect to MongoDB:

  1. Go to the MongoDB Cluster Details page of your newly imported cluster.
  2. Under the Overview tab, find your Credentials and click Show.
  3. Copy your Connection String.
  4. Use these details to update your MongoDB connection to your application, and cancel the previous connecting.

Confirm Your Successful MongoDB Data Migration

After the migration is complete, you'll receive an alert in your ScaleGrid console as well as confirmation to the email associated with your account. Make sure to also confirm the following:

  1. Data size and details match your imported cluster.
  2. Your MongoDB cluster is connected to your application.
  3. Your backup schedule is configured.

Import MongoDB Data From a Remote Server


See how easy it is to import your MongoDB data into your new MongoDB clusters at ScaleGrid.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.