Migration import
Import users, plans, sites, certificates, DNS and balances from another CDN system: dry-run report first, import on confirmation, resumable, no duplicates.
What it solves
Moving from another CDN system, the hard part is bringing over hundreds or thousands of users, sites and balances. Migration import reads the source system directly and produces a dry-run report first (create, merge, rename, skip, conflict, unsupported, each with a reason); you check it before anything runs, and importing the same source again never creates duplicates.
| Source | How it connects |
|---|---|
| Common self-hosted CDN management systems | Administrator API or a read-only MySQL account; pick the system in the source list |
| Cloudflare | API token |
| Bunny CDN | AccessKey |
| Other systems | A generic JSON bundle built from the template, or CSV templates |
Turning it on
Migration import is an official, free plugin of the commercial edition, active once fetched from the plugin store. The community edition does not include it.
- Open System → Migration import, choose the source system and enter the connection details.
- Click Start reading, wait for the dry-run report and check each section (plans, users, user plans, certificates, sites, balances…).
- Confirm, then follow Progress and results; pause and resume as needed.
- Imported balances go to bulk balance approval and are credited only once approved.
Main settings
| Setting | What it does |
|---|---|
| Source name | Tells sources apart; repeat imports deduplicate by it |
| Source on a private network | Allows sources at private addresses |
| Keep source password hashes | Converted on the user's first sign-in, no password reset; kept 7–180 days |
| Default owner | Data without an owner is attached to this user |
Typical uses
- Moving everything from an old system: plans and users first, then sites and certificates, then approve balances.
- Sites already on Cloudflare: import their domains and origins, then put them on your nodes.
Limits and notes
- Source credentials are used only for this read, held in server memory and cleared afterwards, never written to the database or logs.
- Nodes, lines and monitoring are not migrated (nodes are reinstalled on the new system), nor are access logs, statistics or the text of custom WAF/CC rules; the latter are listed as not migrated.
- Hosted CDNs (Cloudflare, Bunny) import domains and origins only; certificate private keys cannot be read and are only listed.
- Private formats of unknown systems cannot be recognised without setup; the report lists the columns it did not recognise.