Migrate Your IMEI Unlock Store Without Losing Wallet Balances

Ask any shop owner why they stay on a platform they have outgrown, and the answer is rarely the software. It is the money sitting in customer wallets. Balances, credits and reseller deposits are liabilities you owe your buyers, so one wrong number during a move turns into a support ticket, a dispute or a lost account.

This guide walks through how to move an existing IMEI unlock store to a new platform while keeping wallet billing intact. It is a software and data plan, nothing more.

Why wallet balances are the hard part of a migration

Products, categories and branding can be rebuilt, and a design can be redone in an afternoon. Wallet data is different, for three reasons:

• It is financial. Every balance represents money a customer paid you in good faith.
• It changes constantly. Orders, refunds and top-ups keep moving the numbers while you plan the switch.
• It has history. Customers and your own bookkeeping expect a trail, not just a final figure.

Treat the migration like closing the books at month end: freeze, reconcile, transfer, verify.

Step 1: Audit what you have before you touch anything

Start with an inventory. Export or record the following from your current panel, whether it runs on DHRU Fusion or another system:

1. Every customer account, with username, email and account type (retail or reseller).
2. The current wallet balance per account, with a timestamp for when you took it.
3. Pending and processing orders, including which supplier each one sits with.
4. Your service list with prices, groups and any per-customer or per-group pricing.
5. Reseller API keys and the integrations that depend on them.

Save these as dated files and keep them somewhere safe. They are your reference point if anything looks off later.

Step 2: Settle open orders and set a freeze window

The cleanest migration has the fewest moving parts. Before cutover, let in-flight orders finish where you can. Orders that are still waiting on a supplier should be listed individually, so you know what to refund or re-place afterwards. No supplier can promise a result in every case, so do not assume pending orders will clear on schedule.

Then pick a short freeze window, ideally at your quietest hour. During that window, pause new top-ups and take your final balance snapshot. Tell customers in advance with a short notice on your storefront and in your messaging channels.

Step 3: Move balances as data, not as manual edits

Re-typing balances by hand is where errors creep in. Instead, load the snapshot in bulk and match accounts on a stable identifier such as email address. A few habits help:

• Total check: the sum of all balances in the old system should equal the sum in the new one, to the cent.
• Spot check: pick a sample of accounts, including your largest resellers, and compare them one by one.
• Zero and negative balances: decide in advance how to treat them, then apply that rule to every account.

If you would rather not run this yourself, GSMSS offers free migration, so you are not left to work out the import alone. Bring your exports and we help you plan the transfer.

Step 4: Keep your reseller API working

If you have resellers who connect through a Fusion API style endpoint, their integrations are as important as their balances. A reseller whose software suddenly stops talking to your store will assume the worst about their credit too.

Check that your new platform exposes a Fusion-compatible reseller API, so existing tools need little more than a new URL and key. Send those details early and offer a test order before the old panel goes quiet.

Step 5: Plan the domain cutover

With white-label hosting, your store runs on your own domain while the platform is hosted for you. That makes cutover mostly a DNS change. Lower your DNS TTL a day or two ahead so the switch propagates faster, and keep the old panel read-only for a few days afterwards. If a customer questions a balance, you can compare against the original data right away.

Step 6: Verify, then communicate

Before reopening top-ups, run a short test pass:

1. Log in as a retail customer and check the balance and order history.
2. Log in as a reseller and place a test order through the API.
3. Add a small test top-up and confirm the wallet updates correctly.
4. Compare the grand total against your frozen snapshot.

Once everything matches, announce the move. Customers mostly care about two things: their balance is intact, and the store works as before.

Comparing platforms fairly

DHRU Fusion is a well-known choice, and many stores run on it successfully, usually on software they install and maintain themselves. A hosted platform changes that trade: you give up some hands-on server control and get updates, hosting and support handled for you. Our DHRU Fusion alternative page lays out the differences so you can decide on facts. Whichever way you go, ask any vendor how balances are imported and verified before you commit.

What it costs to try

GSMSS plans start from $20/month, and there is a 90-day free trial, so you can load a copy of your data, test wallet billing and check your reseller API before you retire the old store. See the current options under pricing.

A good migration is boring. The balances match, the API keys work, and customers barely notice.

Plan the freeze, move data in bulk, reconcile to the cent and keep the old panel for reference. Do those four things and your wallet balances will arrive in the new store exactly as they left the old one.