Switch from Heroku, Railway, Fly.io & Co. to NS10BE – Nightscout Migration

Nightscout Migration

Nightscout Migration – Switch to NS10BE

Heroku discontinued? Railway too expensive? Fly.io too complicated? Render too unreliable? Bring your Nightscout instance to NS10BE in just a few minutes — all historical data comes along, no data loss, no technical knowledge required.

  • ✓ EU servers in Germany — GDPR compliant
  • ✓ Since 2017 — the first Nightscout hoster worldwide
  • ✓ 3-day free trial — no credit card required
  • ✓ Support in German and English via ticket, FB and Discord

Which providers can be migrated?

Both import methods work with the following sources:

Provider API Import * MongoDB Import **
Heroku✓✓
Railway✓✓
Fly.io✓✓
Render✓✓
Google Cloud✓✓
MongoDB Atlas–✓
Northflank✓✓
Azure✓✓
Self-hosted instance✓✓

* API Import works as long as the old Nightscout instance is still reachable.

** MongoDB Import requires the Connection String of the database. For Heroku and Render this is usually MongoDB Atlas — the Connection String can be found in the respective dashboard.

Method 1: API Import — Nightscout to Nightscout

The easiest way. Your old Nightscout instance must still be reachable and active. All CGM entries, treatments and calibrations are transferred directly via API.

Step by step
  1. Create a new server at NS10BE — register for free, create a server, and your new instance is up and running in under 3 seconds.
  2. Start import: In the NS10BE Dashboard → “Import” → “API Import”.
  3. Enter the URL of your old instance — e.g. https://my-name.fly.dev or https://my-name.up.railway.app or https://my-name.onrender.com — and your old API password.
  4. Start import — depending on the amount of data, the import takes a few minutes to hours. You can close the page during this time or check how far the import of your Nightscout data has progressed.
  5. Update your apps: Enter your new NS10BE URL and your new API password in xDrip+, AAPS, Loop, Juggluco etc. You can find instructions in Getting Started → Step 5.
Tip for Railway & Fly.io: Your old instance must still be active for the API Import. With Railway and Fly.io this is the case until you cancel — so start the import before you cancel there.

Method 2: MongoDB Import — Full database transfer

For a complete data migration — ideal if your old instance is already offline, or you want to securely transfer the entire database contents. Works via remote credentials or by uploading mongodump files.

Option A: Remote credentials (Railway, Fly.io, MongoDB Atlas)

With Railway, Fly.io and MongoDB Atlas you can read the MongoDB connection details directly from the dashboard and enter them at NS10BE — the import is then performed automatically.

  1. Copy the MongoDB connection URL (Connection String) from your old provider dashboard:
    • Railway: Project view → Database service → “Connect” → MongoDB Connection URL
    • Fly.io: Fly.io Dashboard → App → Secrets / Environment variables → MONGODB_URI
    • MongoDB Atlas: Atlas Dashboard → Cluster → “Connect” → Connection String
    • Heroku / Render: App settings → Config Vars / Environment variables → MONGODB_URI
  2. In the NS10BE Dashboard: “Import” → “MongoDB Import” → paste Connection String → start import.
  3. Done. All entries, CGM values, treatments, calibrations and profile values are transferred.
Option B: Upload mongodump files

Do you already have a local backup of your MongoDB (.bson files)? Then simply upload all .bson files at once — NS10BE imports them automatically into the selected server.

  1. Create a backup (if not already available) using mongodump on your old instance or via the Atlas dashboard (“Backup” → “Download”).
  2. In the NS10BE Dashboard: “Import” → “MongoDB Import” → select all .bson files at once and upload them.
  3. Import is performed automatically.
No data loss thanks to parallel operation: You can run both instances simultaneously — the old instance stays active, the new NS10BE instance is already running. Only when everything has been transferred and you have updated your apps, you cancel with the old provider. If the testing period was not enough, simply contact us.

After the import: Update your apps

Enter your new NS10BE URL and your API password in all your apps. You can find the exact settings for each app in:

Frequently asked questions about migration

Will I lose data when switching to NS10BE?

No — when done correctly, no data is lost. We recommend parallel operation (old instance stays active until everything is verified) and optionally creating a local backup beforehand.

Does the import work if my Heroku instance is already gone?

If the Nightscout instance is gone but the MongoDB on Atlas still exists, you can use the MongoDB Import via Connection String from Atlas. Atlas databases remain available for some time even after cancelling Heroku.

How long does the import take?

The API Import takes between a few minutes and several hours depending on the amount of data. The MongoDB Import is usually faster. You can check the current status at any time in the NS10BE Dashboard.

What does switching to NS10BE cost?

The first 3 days are free — no risk, no credit card required. After that from €4.99 / month. Import tools are included in the price, the only exception is the MongoDB direct export (€14.99 one-time fee, included with annual subscription).

Do I need technical knowledge?

For the API Import, no — just the URL and password of your old instance. For the MongoDB Import via Connection String, you need to copy the string from the dashboard of your old provider — this is explained with screenshots. If you have any questions, the 10BE support team is happy to help.

Switch now — 3-day free trial

Register at NS10BE for free Questions? We are happy to help
Back to top
↑