Migrating from EasyDCIM to SynergyCP#
This guide walks you through exporting your inventory from EasyDCIM 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#
| EasyDCIM | SynergyCP |
|---|---|
| Devices and items (servers, switches, PDUs, with models, serials, metadata) | Servers, Switches & PDUs |
| Network ports and their switch-port connections | Server network connections |
| Power ports and their PDU outlet connections | Server power connections |
| IPAM subnets, IP addresses, and VLANs | IP Groups & IP Entities |
| Locations and racks | Locations |
| Users and clients | Clients |
| Orders/services (client ↔ device mapping) | Server assignments & Billing IDs |
IPMI credentials are not exposed by the EasyDCIM API — they live in the database. The script can include a database dump when run on the EasyDCIM server itself (recommended), or we’ll collect them together during the assisted migration.
Bandwidth history (InfluxDB/RRD) doesn’t transfer automatically; SynergyCP starts collecting bandwidth from your switches as soon as they’re added. If you bill from EasyDCIM’s usage data, mention it in your ticket and we’ll discuss options.
Using EasyDCIM together with WHMCS? Billing stays in WHMCS — SynergyCP has its own WHMCS integrations, and we’ll help you swap the module over as part of the migration.
Step 1: Create an API token#
The export uses EasyDCIM’s API v3, so you’ll need an admin API token:
- Log into the EasyDCIM admin area.
- Go to the API Tokens section.
- Create a new admin token.
If your EasyDCIM version predates API v3, skip the script and open a ticket — we’ll export your data another way (typically from a database backup).
Step 2: Run the export script#
For the most complete export, run this on the EasyDCIM server itself as root — the script will then offer to include a database dump, which captures IPMI credentials and other details the API can’t provide. It also works from any Linux machine that can reach your EasyDCIM panel (API data only). It needs curl and jq installed.
curl -fsSLO https://distribution.synergycp.com/scripts/migrate-from-easydcim.sh
bash migrate-from-easydcim.shThe script will prompt for your EasyDCIM URL and API token, or you can pass them directly:
EASYDCIM_URL=https://dcim.example.com EASYDCIM_TOKEN=xxxxx bash migrate-from-easydcim.shThe script is read-only against your EasyDCIM data: it only makes GET requests to the API, and the optional database dump uses EasyDCIM’s own backup tooling (
easydcim-control app backup --only-sql) or a plainmysqldump. It never changes your inventory. Feel free to review it before running.
When it finishes, you’ll have an archive named synergycp-migration-easydcim-<date>.tar.gz in the current directory.
Step 3: Send it to us#
The archive may contain credentials — especially if you included the database dump. Store it securely and only share it with SynergyCP support — never post it publicly.
Open a support ticket and attach the archive. Database dumps are often 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 devices, 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. You verify the result, run a few test OS reloads, and cut over on your schedule. Your EasyDCIM installation is never modified.
If something goes wrong#
If the script fails, prints warnings, or your environment is unusual (older EasyDCIM version, API v2 only, Docker specifics, 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.