Migration Window Closed
The legacy quickbox.io platform has retired, and every remaining account was moved to v3.quickbox.io for you. The old-site login and the dashboard Migration Utility are gone because the move is already done. There is nothing left to migrate. The one step left for you is setting your new API key on each server (see below).
Your account moved
Sign in at v3.quickbox.io with the same email and password
Your account came across with the same email and the same password you used on the old site. Sign in and everything is waiting for you: your license, your new API key, and your billing details. The rest of this page covers what to check once you are in.
What Moved For You
Same Sign-In
Your account carries the same email and password from the old site. Sign in at v3.quickbox.io and you are in. No reset is needed.
Set Your Key on Each Server
Your license key moved to the new qbp_ format. Set your new key on each server under System > API Control, or with qb manage api -k. Updates can fail until you do.
A New API Key
A fresh qbp_ API key was created with your license and is waiting in the dashboard under Dashboard > API Keys. Set it on each server under System > API Control.
Your Price Stays
Subscriptions keep the price you were already paying. Nothing about your plan or seat count changed in the move.
Sign In
Go to v3.quickbox.io and sign in with the same email address and password you used on the old quickbox.io site. Your account was created for you with those exact credentials, so there is no separate registration and no password reset to do first.
If you would rather sign in with Discord, that works too, as long as it lands on the account that holds your email.
Use the password reset on the sign-in page. The reset email goes to the address on your account, which is the same one you had on the old site.
Put Your New API Key on Each Server
When your account moved, your license key moved to the new v3 format too. Your new key starts with qbp_. Your servers still have the old quickbox.io key saved, and the QuickBox update tools (qb update and friends) check for the new format, so until a server has the new key its updates can fail.
Copy your new key from Dashboard > API Keys here on v3.quickbox.io, then set it on each server:
- In your QuickBox dashboard: open System > API Control. In the QuickBox Central section, click Edit credentials, paste the new key into API Key, and click Save.
- Or from the command line: run
qb manage api -k qbp_YOUR_NEW_KEY. That swaps the old key out and activates the new one in one step.
Do the same on any new server you set up.
Find Your New API Key
A new qbp_ API key was issued with your license during the move. It lives in the dashboard under Dashboard → API Keys, where you can copy it, see where it is in use, and regenerate it whenever you want.
Your license itself is under Dashboard → Licenses, with your seat count, activation history, and telemetry for each server.
Subscriptions and Billing
If you are on a subscription, two things are worth knowing.
Your price is unchanged. You keep the price you were already paying. The move did not reprice anything.
Set up billing before your access date. Your access on the new platform runs through the date your subscription was already paid through, and never less than two weeks from the day it moved. To keep your subscription going past that date at your current price, add a payment method in the dashboard before then.
Open Dashboard → Billing and add a card or connect PayPal before your access date. If no payment method is on file when that date arrives, the subscription lapses and you would have to start a new one at the current price.
Lifetime keys need nothing here. There is no renewal and no billing to set up.
Finish Up
FAQ
qbp_). Copy it from Dashboard > API Keys, then on each server open System > API Control > QuickBox Central > Edit credentials, paste it into API Key and Save, or run qb manage api -k qbp_YOUR_NEW_KEY. Until then, its updates can fail.qbp_ key was created with your license during the move.Join the Community
Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.