How to Switch Trackers Without Losing Your History

The thing stopping most people from moving to a better tracker is not the setup work. It is the four years of hand-entered transactions sitting in the old one, and the suspicion that leaving means abandoning them.

Start with the reassurance, because it changes how much care this deserves. A tracker never holds your assets. It reads balances through read-only keys and public addresses, and your coins sit on the exchange or in the wallet regardless of which app is looking at them. Switching cannot cost you funds. It can cost you records, which is a real cost worth twenty careful minutes, but it belongs in a completely different risk category than moving money.

What should you export before you touch anything?

Export while the old account is still live and, if it is paid, still paid. Export capability sometimes sits behind the subscription you are about to cancel, and discovering that afterwards is a bad afternoon.

1. Export from the old tracker. CoinStats supports CSV export from both web and mobile, letting you pick transaction history or balances. Delta exports through Settings, with one documented caveat that matters: standard exports include only active transactions, so anything you deleted from your records will be absent from the file. Whatever product you are leaving, read its export documentation rather than assuming the file is complete.
2. Export from each exchange directly. This is the step people skip, and it is the most valuable one. The exchange is the original source; your old tracker holds a re-derived copy of it. Binance documents its transaction history export, and every major venue offers an equivalent. Pull the full history for every account, not just the current year.
3. Record the ground truth. Screenshot or write down the old tracker's totals as of the switch date: portfolio value, total profit and loss, and the cost basis of each significant position. This is what you will reconcile the new app against, and once the old app is gone you cannot get it back.
4. List the accounts. Every exchange, wallet, chain and cold storage address, so nothing gets left behind in the migration. The account you forget is the one that makes the totals disagree later.
5. Note your manual entries separately. The OTC purchase, the peer-to-peer trade, the coins from 2017 with a price you looked up once. These are the records that exist nowhere except inside the old app.

Store the exported files somewhere durable before continuing. They are the only version of your history that no company controls.

What carries over, and what does not?

Understanding the split makes the whole process predictable.

Current balances always carry over, because they are not really carried at all. The new tracker reads them fresh from the exchange API or the chain, so within minutes of connecting, your quantities are correct without any migration having happened.

On-chain history carries over for the same reason. Chain data is public and permanent, and pasting an address into a new app gives it the entire transaction record from genesis. There is nothing to migrate and nothing to lose.

Exchange trade history usually carries over too, because a connected exchange API generally exposes past trades as well as current balances, subject to whatever lookback window that exchange offers.

What does not carry over is everything you created yourself. Manual positions and the acquisition prices you typed into them. Your alerts, all of them, which have to be rebuilt by hand in the new app. Watchlists and any grouping or tagging you set up. Notes on individual transactions. And the old app's computed profit figures, which are derived rather than stored and will be recalculated from scratch under the new app's assumptions.

Budget an evening for rebuilding manual entries and alerts. That is the actual cost of switching, and it is the honest number.

How do you rebuild cost basis without guessing?

This is where switches go quietly wrong, and the failure has a signature you can recognise.

When a new tracker imports a transfer between two accounts you own, it frequently reads it as a deposit with no acquisition price attached. The app assumes zero, and the entire position shows up as pure profit. A portfolio that suddenly reports a spectacular unrealised gain after a migration has not discovered anything about the market. It has lost your cost basis. Cost basis vs. market value covers how to identify and repair this.

The fix is unglamorous. Work down from your largest positions, because a wrong basis on your biggest holding distorts the total and a wrong basis on a $40 position does not. For each one, find the real acquisition in the exchange export you pulled in step two, and enter it. Adding a manual position walks through the fields; the acquisition date and price are the two that matter, and everything else is optional.

Positions you genuinely cannot price get a defensible estimate and a note saying it is an estimate. What you should not do is leave them at zero, because zero is not a neutral placeholder. It is an active claim that you paid nothing, and it propagates into every performance number the app shows you afterwards. Unrealised vs. realised profit explains which figures this corrupts.

One boundary worth stating: if you need audit-grade lot tracking for a tax filing, a portfolio tracker is the wrong instrument and always was. Trackers vs. tax software covers where that line sits.

Why run both apps for a month?

Because a tracker reveals its gaps under use, not under evaluation, and the gaps take a few weeks to surface.

Running both costs nothing and risks nothing. Two trackers holding read-only keys to the same exchange account do not conflict, because read-only access cannot change state. Whether it is safe to connect an exchange covers why that is true rather than merely claimed.

Compare four specific things over the parallel period. Do the portfolio totals agree, and if not, which account is responsible? Do the per-account subtotals agree, which localises any disagreement immediately? Do alerts in the new app fire when you expect, on conditions you can verify independently? And when something unusual happens, a token rename or a staking reward or a chain you rarely touch, does the new app handle it without you intervening?

At the end of the period, take one final export from the old tracker, cancel it, and then revoke the API keys it was using. Revoking an API key covers doing that properly on each exchange. A key belonging to an app you have stopped opening is a key nobody is watching, and cleaning it up is the last step of the switch rather than an optional one.

Do that once and the migration is genuinely finished. The next time you consider moving, you will already have the exports, the ground-truth numbers and the account list, which is why the discipline worth keeping is exporting once a quarter whether or not you plan to leave. The people who found that useful were mostly the ones who had not planned to leave.

---

Competitor export documentation referenced above was verified in September 2026 from each provider's own help centre. Export behaviour changes — check current documentation before relying on it.