Switching panels is scary for one simple reason: your whole operation lives inside it. Customers, expiration dates, resellers, credit balances, plans, coupons. Losing any of that means customers complaining, resellers asking questions and you retyping records by hand.
That is why Painel Blend has a dedicated tool for anyone coming from Sigma. The promise is straightforward: Sigma migration in 5 minutes with all your data. In practice it takes about 5 minutes, depending on the size of your base. This guide covers what gets migrated, how to prepare and the full step-by-step.
What comes along
Before importing anything, the panel reads the exported file and shows a summary of what it found, so you can review everything before confirming. The migration covers:
- Active and deleted customers
- Resellers, with the same hierarchy (master, reseller, sub-reseller)
- Credit transactions
- Packages and plans
- Membership plans
- Credit packages
- Discount coupons
- Contacts
- Per-server counts and Max Player customers
Resellers arrive with the same role and keep logging in with the password they already use. No need to message every reseller about new credentials.
Checklist before you start
A smooth migration starts with ten minutes of preparation:
- Super admin access on Sigma. The export script must run while logged in with that profile.
- Your Sigma API token. You will find it under Settings › Developers.
- Servers registered in Painel Blend. Every customer is tied to a server, so add yours before importing.
- A desktop browser. The script runs in a browser tab (Chrome works well).
- A quiet time slot. Not mandatory, but it avoids someone renewing on Sigma mid-process.
Step-by-step
1. Grab the token and copy the script
On Sigma, go to Settings › Developers, accept the terms and copy the API token. In Painel Blend, open the Sigma migration, paste the token and copy the script. The token lives only inside the copied script: it is not stored by Painel Blend.
2. Run the script in the Sigma tab
Go back to the Sigma tab, open the browser console and paste the script. If Chrome warns you about pasting code, type allow pasting and press Enter. When it finishes you will see “Export completed” and a sigma-export-YYYY-MM-DD.json file is downloaded.
3. Upload the file and review the summary
Upload the file to Painel Blend. The panel shows the summary with counts of customers, resellers, credits, plans, coupons and customers per server. This is the moment to compare the numbers with what you know about your base.
4. Pick the import options
This is where you decide how the import behaves:
| Option | When to use it |
|---|---|
| Import only resellers and customers that exist on the server | When you only want what is active on the chosen server |
| Wipe the current panel data before importing | When you already experimented in the panel and want a clean start |
If you choose to wipe, current customers and resellers move to “Deleted” (they can be restored) and current plans and credit packages are deactivated. Lines on the server are not touched. To confirm, the panel asks you to type a confirmation word.
Customers that already exist on the server are simply linked: nothing gets duplicated.
5. Follow the progress
Once confirmed, the import starts and you follow the progress live, with a log of each step. No need to keep refreshing the page.
After the migration: what to check
Done? Run a quick check before telling your team:
- Open a few customers and confirm expiration, server and connection limit.
- Log in as a test reseller and make sure the credit balance matches.
- Review plans and credit packages under Prices.
- Generate a new token on Sigma. The old one was used in the script; rotating it is good security practice.
If the result is not what you expected, you can undo the import: everything it brought in leaves the panel and what was there before comes back. Nothing changes on the server.
Common mistakes (and how to avoid them)
Running the script without super admin access. The export ends up incomplete. Log in with the right profile first.
Skipping server setup. Without servers in Painel Blend there is nowhere to attach customers. Register first, import second.
Ignoring the summary. It exists so you can check the numbers before confirming. If something looks off, stop and investigate.
Selling on Sigma during the migration. A renewal made mid-process may be missing from the file. Agree on a short pause with your team.
Forgetting to tell resellers. They keep the same password, but they need the new panel address. If you use your own domain, see the guide on white label with your own domain.
What comes next
With your base inside Painel Blend, it is a good time to automate what used to be manual. A solid next step is turning on automatic Pix renewals, so customers pay and get renewed without you stepping in.
Ready to migrate?
See every detail of the tool on the Sigma migration page. Want to try it with your own base? Request access to the closed beta or join the waitlist.
