Trading a pump.fun Coin After Migration to PumpSwap
What changes when a pump.fun coin completes its bonding curve and moves to PumpSwap: where trades go, why old tools fail with error 6005, and what to check first.
By DevBundler Team · · 5 min read
The short answer
Once a pump.fun coin's bonding curve completes, the coin migrates to PumpSwap, pump.fun's AMM, and all trading moves to a pool there. Buys sent to the old curve fail with error 6005 BondingCurveComplete. You trade the same token from the same wallets, but your tool has to route trades to the pool. DevBundler switches automatically.
Key takeaways
- Migration happens when the curve has sold its 79.31% of supply; after that the curve refuses buys with error 6005.
- After migration the coin trades in a PumpSwap pool, where the price comes from the pool's reserves instead of the curve.
- Your tokens stay in your wallets. Nothing needs to be claimed or converted.
- Slippage and price impact still apply: your trade moves the pool's price and so does everyone else's.
- DevBundler's trading bar switches to PumpSwap automatically, so batch trades across wallets keep working.
Your coin just filled its bonding curve. The progress bar hit 100%, and a minute later your usual sell button throws "custom program error 6005". Nothing is broken. The coin has moved house, and your trades need the new address.
This post is about that new house: what PumpSwap is, what changes for a trader, and what to check before you buy or sell after migration.
What migration means for a trader
Every pump.fun coin starts on a bonding curve that sells tokens directly to buyers. On mainnet it sells 79.31% of supply. When the last of those tokens is bought, the curve completes and the coin migrates to PumpSwap, pump.fun's AMM.
Bonding curve
buys and sells trade directly with the curve
Curve completes
its 79.31% of supply has been sold
Migration
the coin gets a PumpSwap pool
PumpSwap trading
all trades now go through the pool
From that point the curve is closed. Any buy aimed at it gets rejected by the pump.fun program with error 6005 BondingCurveComplete. The token itself does not change: same mint, same 1,000,000,000 supply, same 6 decimals, same balances in your wallets. What changes is where you trade it.
For the mechanics of the migration itself, see what happens when the bonding curve completes.
Curve vs pool: what is different?
Trading on the curve vs trading on PumpSwap
| Bonding curve | PumpSwap pool | |
|---|---|---|
| Who you trade with | The curve itself | A liquidity pool |
| What sets the price | How many tokens the curve has sold | The ratio of the pool's reserves |
| Can it run out? | Yes, it completes at 79.31% sold | No fixed end point |
| Failure if you target the wrong one | Curve trades after completion fail with 6005 | Pool trades before migration have no pool to use |
| Slippage | Applies | Applies |
The big practical difference is that the curve has an end and the pool does not. On the curve, every buy brings the coin closer to completion. On PumpSwap there is no progress bar to fill. The price simply moves with buys and sells against the pool.
What stays the same: your trades still move the price, and so do other people's. A buy pushes the price up, a sell pushes it down, and the bigger the trade relative to the pool, the bigger the move. Slippage limits still protect you from a fill much worse than your quote. Slippage on pump.fun explained covers how to set them.
Why old tools break at migration
Plenty of scripts and tools are written for the curve only. They build a pump.fun buy or sell instruction against the coin's bonding curve and send it. After migration the curve is finished, so the program rejects the trade.
The symptoms:
- Buys fail with 6005 BondingCurveComplete.
- Sells sent to the curve fail too, because the curve no longer trades.
- Price quotes from the tool stop moving, because it is still reading the frozen curve.
If you see any of these right after a coin hits 100%, the tool needs to route to PumpSwap. In DevBundler that happens automatically: once the curve completes, the trading bar on the coin's dashboard switches to PumpSwap, and buying and selling across your wallets works the same way it did before.
What to check before trading after migration
Before your first post-migration trade
- Confirm the coin has actually migrated. The progress bar should read 100% and the curve should be marked complete.
- Make sure your tool trades on PumpSwap, not the old curve.
- Look at your slippage setting again. Migration is often a busy moment, and prices can swing.
- Keep SOL for fees in every wallet you plan to trade from.
- Check how much of the supply your own wallets hold, and what that looks like to other holders.
Multi-wallet trading on PumpSwap
The batch problem that affects curve trades applies to pool trades too. If you sell from six wallets and all six are quoted against the same pool state, the first sale lowers the price and the later ones miss their minimum SOL out. DevBundler quotes every wallet in a batch in the order it will be sent, against the state left by the wallets before it, on the curve and on PumpSwap.
On mainnet you can still pick Fast mode (each wallet sends its own transaction straight away) or Bundle mode on Premium (all wallets in one Jito bundle, same block, all or nothing). Speed presets set the priority fee, which helps trades land when migration traffic is heavy. How to sell across multiple wallets walks through the full flow.
Your launch wallets after migration
DevBundler keeps showing your wallets' combined share of supply on the dashboard after migration, the same as before. If you planned to take some profit around completion, the same principles apply as on the curve: keep it in proportion and stick to the plan you set. Holders who feel surprised at migration tend not to stay.
Migration is not a finish line
It is tempting to treat completion as a win, and for a launch it is a milestone. But a migrated coin is still a speculative asset. Buyers can leave a PumpSwap pool just as easily as they left a curve, and there is no curve completion left to aim for. Whatever plan you had for selling should still apply after migration, adjusted for the new venue. If you never wrote one, planning your exit on a meme coin is a place to start.
Frequently asked questions
›What is PumpSwap?
PumpSwap is pump.fun's automated market maker (AMM). When a coin's bonding curve completes, the coin migrates there and trades against a liquidity pool instead of the curve.
›Why can't I buy on the bonding curve anymore?
Because it completed. The pump.fun program refuses curve trades on a finished curve with error 6005 BondingCurveComplete, so trades need to go to the PumpSwap pool instead.
›Do I need to do anything with my tokens after migration?
No. The tokens in your wallets are the same tokens with the same mint. You can hold them or trade them on PumpSwap with any tool that supports it.
›Does DevBundler support trading after migration?
Yes. Once the curve completes, the trading bar on the coin's dashboard switches to PumpSwap automatically, so you can keep buying and selling across your wallets.
›How much does the market cap need to be for a pump.fun coin to migrate?
Migration is triggered by the curve selling all of its tokens, not by a fixed dollar figure. The SOL and USD amounts involved change with fees, SOL's price and pump.fun's settings, so check current figures.
Keep reading
What Happens When the pump.fun Bonding Curve Completes
When a pump.fun bonding curve sells its 79.31% of supply, it completes and the coin migrates to PumpSwap. What changes for trading, prices, errors and your wallets.
· 5 min read
Reading the pump.fun Bonding Curve Progress Bar
What the pump.fun bonding curve progress percentage measures, why it can go down, why the last stretch costs far more SOL, and what happens when it hits 100%.
· 4 min read
Slippage on pump.fun Explained: Settings, Errors and Fixes
What slippage means on pump.fun, why trades fail with errors 6002 and 6003, how to choose a slippage setting, and how batch trades keep later wallets inside it.
· 5 min read