Migrating from NOC-PS to SynergyCP#

This guide walks you through exporting your inventory from NOC-PS 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#

IPMI passwords need special handling. The NOC-PS API never returns stored IPMI passwords — only a flag saying whether one is set. The script grabs NOC-PS’s own CSV export, which may include them; if it doesn’t, we’ll retrieve them with you from the appliance console (NOC-PS stores its data in a local PostgreSQL database) as part of the assisted migration. Either way, it’s a solved problem — just mention it in your ticket.

Bandwidth and power usage history doesn’t transfer automatically; SynergyCP starts collecting bandwidth from your switches as soon as they’re added.

Step 1: Create an API user#

The export uses the NOC-PS JSON-RPC API with regular web UI credentials. Any NOC-PS user works, but we recommend a dedicated one:

1. Log into the NOC-PS web interface.
2. Go to start → users → add and create a user for the export.

Step 2: Run the export script#

Run this on any Linux machine that can reach your NOC-PS appliance over HTTPS. It needs curl and jq installed. (Don’t run it on the appliance itself — NOC-PS runs a minimal custom Linux without these tools.)

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

The script will prompt for your NOC-PS URL and credentials, or you can pass them directly:

NOCPS_URL=https://nocps.example.com NOCPS_USER=apiuser NOCPS_PASS=secret bash migrate-from-nocps.sh

The script is read-only: it only calls NOC-PS list/get API methods and downloads the same CSV export available in the web UI under start → Misc settings → Import/Export. It never changes anything on your appliance. NOC-PS appliances ship with a self-signed certificate, so the script skips TLS verification when talking to it. Feel free to review the script before running.

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

If you can’t run the script at all, the manual fallback is: log into the NOC-PS web UI, go to start → Misc settings → Import/Export, download the export ZIP, and attach that to your ticket instead.

Step 3: Send it to us#

The archive may contain credentials. 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 hosts, subnets, and devices should be represented in SynergyCP, and then write and run an import tailored to your data — including the IPMI credentials handling described above. You verify the result, run a few test OS reloads, and cut over on your schedule. Your NOC-PS appliance is never modified, so it keeps working throughout.

If something goes wrong#

If the script fails, prints warnings, or your NOC-PS version behaves differently than expected (the product has been around a long time and versions vary), 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.