Migrating from Tenantos to SynergyCP#

This guide walks you through exporting your inventory from Tenantos so that our team can migrate it into SynergyCP for you.

This migration is free. The export script below is the fast path, but it is entirely optional — if anything doesn’t work, or you’d simply rather have us handle everything, open a ticket and we’ll do the migration with you.

What gets migrated#

A few things don’t transfer automatically, and we handle them together during the assisted migration: reverse DNS records (see our rDNS package, which can import your existing zones), bandwidth history, and user passwords (Tenantos only stores hashes, so your clients will set new passwords in SynergyCP).

Using WHMCS with Tenantos?#

If your WHMCS installation provisions servers through the Tenantos WHMCS module, the last step of the cutover is swapping that module for ours. Billing stays in WHMCS throughout — your clients’ accounts, invoices, and services are untouched; only the provisioning module behind each product changes.

The swap happens after your servers are imported into SynergyCP:

1. Install our WHMCS module alongside the Tenantos one — the two can coexist while you transition. (A Reseller variant is also available if you resell through WHMCS.)
2. As part of the import, we set each SynergyCP server’s Billing ID to its WHMCS service ID — that’s how SynergyCP links a server to a WHMCS service (see Billing IDs). We build this mapping from your Tenantos export, so it’s part of the free migration rather than something you do by hand.
3. Switch each WHMCS product from the Tenantos module to the SynergyCP module.
4. Verify SSO, provisioning, and server controls work through the new module on a test service, then remove the Tenantos module.

Mention in your ticket that you use WHMCS and we’ll plan the module swap with you as part of the migration.

Step 1: Create an API token#

The export uses the Tenantos REST API, so you’ll need an API token from an admin user:

1. Log into Tenantos as an administrator.
2. Open your account settings and go to API Keys.
3. Create a new token. If you restrict it by IP, allow the machine you’ll run the script from.

Step 2: Run the export script#

Run this on any Linux machine that can reach your Tenantos panel (the Tenantos server itself works fine). It needs curl and jq installed.

curl -fsSLO https://distribution.synergycp.com/scripts/migrate-from-tenantos.sh
bash migrate-from-tenantos.sh

The script will prompt for your Tenantos URL and API token, or you can pass them directly:

TENANTOS_URL=https://platform.example.com TENANTOS_TOKEN=xxxxx bash migrate-from-tenantos.sh

The script is read-only: it only makes GET requests against the Tenantos API and never changes anything in your installation. Feel free to review it before running.

When it finishes, you’ll have an archive named synergycp-migration-tenantos-<date>.tar.gz in the current directory.

Step 3: Send it to us#

The archive contains device credentials (IPMI passwords, switch and PDU logins). Store it securely and only share it with SynergyCP support — never post it publicly.

Open a support ticket and attach the archive. If it’s too large to attach, just say so in the ticket and we’ll provide a secure upload location.

What happens next#

We review the export with you, confirm how your servers, IP space, and clients should be represented in SynergyCP, and then write and run an import tailored to your data — including anything the script couldn’t capture. In many cases we’ll ask for temporary access to your Tenantos database so nothing is missed. You verify the result, run a few test OS reloads, and cut over on your schedule. Your Tenantos installation is never modified.

If something goes wrong#

If the script fails, prints warnings, or your environment is unusual (older Tenantos version, network restrictions, a huge fleet), don’t spend time fighting it — open a ticket, paste the script output, and we’ll gather the data together and complete your migration for free.