Migrate from Content Central to Nucleus One
The built-in migration path: generate a Nucleus One API key, connect Content Central's Migrate to Nucleus One page with it, choose how missing files are handled, and understand the catch-up phase before the migration is finalized.
Before you begin
- A Nucleus One organization you administer
- Content Central administrator access with the Integrations permission
At the end of this guide the migration is connected and running: Content Central pushes its catalogs, users, and documents into your Nucleus One organization, keeps forwarding newly captured documents while both systems run side by side, and waits for you to finalize when you're ready to cut over.
The migration is driven from the Content Central side — Nucleus One's only job in the setup is to issue the API key that authorizes it. That design has a practical consequence: you do the work in your existing Content Central administration area, and you watch the results appear in Nucleus One.
Step 1 — Generate the API key in Nucleus One
In Nucleus One, open the avatar menu at the top right and choose API Keys.
Click +, and in the Add API Key dialog give it a Name/Description that says what it's for —
Content Central migration— then click ADD.
Copy the key from the API Key Created alert now. The warning is literal: "This is the ONLY time you will see this key." Keep it in a safe place, and don't commit it to any version control system.
The Add API Key dialog and the one-time API Key Created alert
Step 2 — Connect Content Central
In Content Central, open Administration and choose Migrate to Nucleus One. On current versions this page opens in the Classic interface — if you don't see the entry, browse directly to
/Admin/AdminMigrateToNucleusOne.aspxunder your Content Central address and it will switch views for you. You need the Integrations administration permission to use it.
Paste the key into Nucleus One API Key: (the field is masked, like a password).
Once the key is accepted, pick the Destination Nucleus One Organization: from the drop-down — the list comes from the organizations your key can reach.
Choose the Missing Document-File Handling: policy:
Option Behavior Stop migration with error The migration halts when a document's file can't be found on disk, and waits for you to intervene Permissive The migration records the problem and keeps going On a long-lived system with years of history, some missing files are likely. Stop migration with error is the right choice when you need to account for every document; Permissive is the right choice when finishing matters more than a perfect ledger. Either way the page's View Migration Log shows what happened.
Step 3 — Let it run, and read the status
The page tracks the migration in three sections — Catalogs & Document Types, Users, then Documents — with an overall Migration Status above them. Structure and people go first; documents are the long tail.
Two things to know while it runs:
- It needs intervention loudly, not silently. If something stops the migration, Content Central tells you it "needs user intervention before it can continue" and points you back to this page's status.
- It's not a snapshot — it's a bridge. When the initial pass completes, newly captured documents in Content Central continue to be migrated to Nucleus One until the migration is finalized. You can keep operating in Content Central during the transition without losing anything on the other side.
Step 4 — Verify, then finalize
When the status reports the migration complete, review the results in Nucleus One before touching anything else: spot-check documents against their Content Central originals, and confirm your people arrived — then wire up their access with project members and groups.
Content Central's workflow engine also carries a Migration Verification & Finalization action group for this phase: a verification action that confirms a migrated document was successfully processed by Nucleus One, and a finalization action that ends the migration by removing the connections between the two systems. Neither takes any configuration. Finalization is the point of no return for the bridge — after it, new Content Central captures stay in Content Central — so it belongs at the end of your cutover checklist, not the beginning.
Success check: pick a handful of documents of different types and ages in Content Central and find each one in Nucleus One with its fields intact; capture one new test document in Content Central and watch it arrive in Nucleus One without any action on your part. That pair proves both the history and the bridge.