Skip to Content
DocsV3 PortalMigration Utility

Migration Utility

Bring your license forward

Move from quickbox.io → v3.quickbox.io in minutes

The Migration Utility inside the v3 dashboard walks you through verifying your legacy quickbox.io account, cloning your activations, generating a V3 API key, and safely retiring the old one. Follow this guide to complete the process without downtime. Enable the utility from your dashboard settings if you don’t see it yet. Settings → Preferences → Enable Legacy License Migration.

Enable Legacy License Migration

Open Migration Utility

What Happens During Migration

🧾 Account Verification

Sign in with your quickbox.io username + password to prove ownership before any changes occur.

🔁 Activation Parity

Your V3 license inherits the same activation count, seat limits, and plan perks.

🧩 Order Timeline

A migration receipt is saved so you can track exactly when the switch happened.

🛡️ Safe Deactivation

Old API keys are retired automatically so you don't get duplicate activations or billing surprises.

One-Time Workflow

Each legacy quickbox.io API key can only be migrated once. If you stop part-way through, simply reopen the Migration Utility—the system will resume from the last successful step.

Before You Begin

  1. Locate your current API key on a server with QuickBox Pro installed. Run qb manage api to copy the existing key.
  2. Have your quickbox.io login handy—you’ll sign in with the username/email and password that you used on the legacy site.
  3. Sign in to v3.quickbox.io  and navigate to Settings → Preferences to enable the Migration Utility.
  4. Ensure billing access—subscription/lifetime license owners can run migrations and manage renewals.

Active Subscriptions Only

The Migration Utility only supports active legacy quickbox.io subscriptions or lifetime keys. If your account is suspended or cancelled, contact support before proceeding.

Step 1 – Verify Your Legacy License

  1. Navigate to Dashboard → Migration Utility.
  2. Enter your quickbox.io username/email and password when prompted.
  3. Paste your legacy API key (and optional instance ID) into the form.
  4. Click Verify License.

During verification the utility signs you into your legacy account, confirms that the API key belongs to you, and checks for any blockers (like unpaid invoices or already-migrated keys).

Possible Verification States

Ready

Subscription and API key ownership confirmed. Continue to execution.

Action Required

Ownership confirmed but open invoices or unsupported plan type detected. Resolve billing first.

Blocked

API key already migrated or subscription cancelled. Open a thread in our Discord support channel with the error code.

Save the Verification ID

A UUID is generated for every verification attempt. If you need help from support, provide this ID so we can replay logs instantly.

Step 2 – Execute the Migration

Once verification shows Ready, scroll down and click Migrate. You’ll see a confirmation modal outlining the changes—check the “I Understand” box and press Execute Migration. Behind the scenes we:

  1. Create a $0 migration receipt so your account history stays intact.
  2. Provision a V3 license that mirrors your activation count.
  3. Issue a modern qbp_******** API key + seat tokens.
  4. Update the migration record with lineage data.
  5. Retire every legacy activation that matches the provided instances.

Optional Legacy Deactivation

Checking “I have deactivated my old servers” lets you skip automatic deactivation. Leave it unchecked to let the utility clean up for you.

Step 3 – Update Your Servers

After the success screen, use the new API key everywhere QuickBox is installed.

# On each server previously using the legacy quickbox.io key
qb manage api -o deactivate
qb manage api -k qbp_your_new_key_here
qb manage telemetry -o on
  • If you supplied instance IDs during verification, the utility will list which ones still need attention.
  • Regenerate keys any time from Dashboard → API Keys once migration is complete.

Keep Legacy Keys Offline

Do not reactivate your legacy key after migration. Doing so can trigger rate limiting or a suspension since both systems will see duplicate activations.

Step 4 – Confirm Billing & Access

Use these touchpoints to finish onboarding:

API Keys

Learn every flag exposed by `qb manage api` in v3.

Licenses Dashboard

View seat usage, regenerate keys, and download invoices.

Billing Handoff

Set up billing so renewals continue after your legacy period ends.

Discord Support Thread

Open a thread in #🐧quickbox-and-advanced-linux for live staff assistance.

FAQ

No. Your existing term stays active until the expiration date that was already listed on quickbox.io, but all management now happens from the v3 dashboard.
Yes—repeat the verification flow for every API key tied to your account. Each key produces its own migration receipt, new license, and API key.
No re-installation is required. Simply replace the API key on each server with qb manage api and let the system reactivate against V3.
Turning telemetry on (qb manage telemetry -o on) gives the dashboard immediate health, activation, and usage data for your new license.
Head to the 🐧 quickbox-and-advanced-linux channel on Discord and open a support thread. Our staff will jump in live—no tickets required.

Join the Community

Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.

Dedicated Support
Feature Previews
Community Configs
Active Discussions
Join Discord Server
Rewards