Exchange Mergers: What Changes for Your Balance

An exchange merger is, from a customer’s side, a change of counterparty rather than a change of balance. The number on your dashboard usually stays the same on the first day. What changes is the legal entity that now owes you that number, the ledger that records it, and the procedure you would follow to get it out. An exchange merger at any scale runs on that same logic.

That distinction matters because a balance on a centralized venue is rarely a labelled pile of coins. It is an entry in a database, backed by a promise. When two venues combine, one ledger is migrated into another and every promise is re-papered. The exchange merger itself is mostly invisible from outside; the migration work around it is where users actually feel something.

• A merger swaps the counterparty behind your balance; the displayed figure is not proof that anything moved on-chain.
• Migrations commonly damage the details people rely on later: cost basis lots, withdrawal allowlists, API keys and statement history.
• Withdrawal freezes and re-verification requests are the two moments where access is actually lost, not the announcement day.
• Export statements and reconcile lots before the migration window, not after the old interface goes read-only.

What an exchange merger actually transfers

It transfers a book of liabilities, not a vault. A centralized venue records customer balances in an internal ledger and holds the underlying assets in a mix of hot wallets, cold storage and omnibus accounts. In a merger, the surviving entity takes on the ledger and the obligation to honour it.

Custodial balances are claims

Your balance is a claim on the venue, ranked alongside every other customer claim. Whether that claim is protected, and to what extent, depends on the structure of the deal, the segregation practices of both entities, and the insolvency rules of the jurisdiction where the surviving entity is licensed. None of that is usually explained in the customer email.

A merger can be announced as a technology integration while being, legally, an assignment of customer contracts to a company in another country. The change of governing law often has the largest practical effect on a balance.

On-chain balances are untouched

Assets you hold in a self-custody wallet do not participate in any of this. No migration touches them, no re-verification applies, and no withdrawal window constrains them. That asymmetry is why some holders move to self-custody around a merger announcement, and why others do not bother.

Four things that can move after an exchange merger

1. Deposit addresses

Addresses issued by the old platform can stop being credited after a cut-off. In many migrations the old address continues to forward for a period, then silently stops. A deposit sent to a retired address may require a manual recovery request, which is typically slow and sometimes charged.

Addresses saved in a notes app go stale silently.

2. Fee tiers, withdrawal limits and minimums

Fee schedules are commercial terms, and commercial terms are usually renegotiated as part of the deal. A tier you earned through volume on the smaller venue may not carry over at the same level. Withdrawal minimums can rise, which matters more than the fee itself for small balances.

3. Statements and cost basis

Trade history is often the first casualty. The surviving platform may import balances and open orders but not the full fill-by-fill history that tax reporting depends on. Once the old interface is retired, that export path is gone.

4. Access controls

Two-factor methods, trusted devices and withdrawal allowlists are frequently reset as a security measure. That is a sound default, but a planned withdrawal can then be delayed by the new cooldown period.

The cost side: what a migration can charge you

The visible cost is fees; the larger cost is timing. A withdrawal freeze forces holders who wanted to move to wait, which is exposure to whatever the market does meanwhile. That exposure is not a fee on any statement, but it is real.

Secondary costs are administrative. Re-verifying identity, re-adding beneficiaries and rebuilding API keys all take hours, and those hours have a price for anyone running a business on the venue.

A merged balance is only worth what the entity now holding it can pay, on the day you ask. Announcements describe the technology; the terms describe the claim.

Reconciling a merged account: a worked example

Suppose you accumulated 0.60 BTC across three purchases on the old venue: 0.30 at 28,000, 0.20 at 41,000, and 0.10 at 52,000. Total cost is 8,400 + 8,200 + 5,200 = 21,800, which gives an average of 21,800 ÷ 0.60 = 36,333.33 per coin.

After migration, the new ledger often shows a single 0.60 BTC position with one blended cost figure, or with no cost figure at all. The lots have collapsed into an average. Now suppose you later sell 0.25 BTC at 60,000 for proceeds of 15,000.

Under the flat average the platform reports, the basis consumed is 0.25 × 36,333.33 = 9,083.33, so the recorded gain is 5,916.67. Under a first-in-first-out method, the same sale would consume the 0.30 lot bought at 28,000, giving a basis of 7,000 and a gain of 8,000. The difference in recorded gain is 2,083.33 on a single sale, purely from which lot the method assigns.

Which method applies is a question for local tax rules. Either way you need the original lots, and the merged platform may no longer have them. Rules differ by jurisdiction, so confirm the treatment locally.

What to do in the migration window

1. Export the full transaction history as CSV, plus monthly statements, and store two copies in different places.
2. Record the balance, the asset list and the timestamp on the day before the freeze, so you can prove what you held.
3. Reconcile cost basis lots into your own spreadsheet rather than trusting a blended average.
4. Decide deliberately whether the balance stays or moves to self-custody; write the decision down with a reason.
5. Re-copy deposit addresses from the new interface and delete stale ones from saved lists.
6. Re-create API keys after the migration and revoke anything issued by the old platform.
7. Test a small withdrawal first, then confirm the amount that lands matches what you expected after fees.