TLDR
A token migration can preserve units while changing what the account holder can do with them. Kraken’s guidance, updated October 1, says REP and REPV2 convert to AUGUR at 1:1, with only withdrawals available to EEA and Canadian clients. This October 16 review concerns existing guidance, not a newly announced migration. Kraken migration notice
Key takeaways
- Separate the balance record, service permissions and receiving destination.
- A conversion ratio is not a price guarantee.
- Resolve missing records or uncertain token identity before submitting a transfer.
Market context: a new ticker can hide a change in access
Kraken’s notice describes a July 27–31, 2026 migration window and says it handles custodial balances automatically. The old REP and REPV2 services will not reopen. It attributes the regional restriction to AUGUR lacking a MiCA whitepaper required for its EEA listing, with Canadian trades routed through the same entity. It says access may change if a whitepaper is filed. Timeline and regional explanation
That is Kraken’s platform-specific explanation, not a finding that Canadian law generally requires MiCA documentation. The notice’s historical schedule also does not verify completion in any particular account. Review the ledger and current permissions directly.
Decision checklist: establish the facts before moving tokens
- Reconcile quantities. Download the relevant account history. Identify the old asset debit, new asset credit and any intervening transfers. If the records cannot be reconciled, preserve them and ask support to explain the difference.
- Inspect available actions. Record what the authenticated account allows today. A visible balance, a price chart and an enabled withdrawal form answer different questions. Do not infer one permission from another.
- Identify the receiving asset. Ask the destination to confirm the exact migrated token and network it accepts. Where a contract address applies, compare that identifier using official receiving instructions. Matching names alone are inadequate evidence.
- Price the transfer itself. Check the withdrawal fee and both platforms’ minimums. A small balance can be visible but too small to transfer. A test amount must still meet the receiving minimum after deductions.
- Define success before submitting. Record the destination, expected net amount and how receipt will be confirmed. For an exchange destination, a blockchain transaction is only part of the record; check the credited account balance as well.
Kraken’s withdrawal guide instructs users to match the receiving network, meet the minimum and review the destination address. It warns that an incompatible network can cause permanent loss. Its activity tab shows withdrawal status. Official withdrawal instructions
Compare evidence, not just interface labels
| Evidence | What it helps establish | What still needs checking |
|---|---|---|
| Migration ledger entries | How token units changed in the account | Current permissions and unresolved discrepancies |
| Displayed valuation | The interface’s reference value | Whether an executable market is available to this account |
| Enabled withdrawal form | A route that can be reviewed | Holds, minimums, fees and receiving compatibility |
| Transaction reference | A traceable transfer record | Receipt and usable credit at the destination |
Risk notes: where a routine migration review can go wrong
Assumed liquidity. Do not treat a displayed currency value as proceeds you can obtain. Before relying on an exit route, establish whether you can access it and inspect its actual terms. This article makes no recommendation to buy, sell or hold AUGUR.
Unverified destination. An exchange listing with a similar ticker is not enough to establish that it accepts the migrated asset. If the destination cannot confirm compatibility, stop the transfer preparation and seek clarification.
Fake migration assistance. Treat unsolicited offers to repair a balance as unverified. Open the platform through a saved address or installed app, and use its support channel. Do not disclose a recovery phrase or approve an unfamiliar wallet transaction to prove ownership of an exchange balance.
Incomplete records. Save the notice, account history and support case references with dates. This makes a later dispute or reconciliation easier to explain without relying on screenshots of a changing portfolio total.
CryptoGuide take
The useful measure of a migration is whether a user can reconcile the asset and understand the remaining service options. A renamed balance is only one part of that work. Platforms earn trust when they explain regional restrictions and provide enough transaction detail for users to verify the outcome themselves.
FAQ
Does a one-for-one migration preserve market value?
No. A unit conversion ratio describes token quantity. It does not promise a cash value, available buyer or executable sale price.
What if my account record does not reconcile?
Save the before-and-after quantities and transaction references, then contact support through the authenticated platform. Avoid submitting another transfer while the discrepancy is unresolved.
Should I trust an old deposit address?
Verify current receiving instructions for the exact token and network. A previously successful deposit does not establish compatibility after a token migration.
Conclusion
Start with the ledger, then confirm permissions and destination compatibility. Keep the evidence for each step. If any link is uncertain, resolve it through official support before making an irreversible transfer.
Related pages
Sources
Primary sources reviewed October 16, 2026. The checklist and comparison are CryptoGuide editorial analysis. No private account, transfer or live trading availability was tested.
- Kraken: REP and REPV2 migration to AUGUR, updated October 1, 2026
- Kraken: cryptocurrency withdrawal guide, updated August 19, 2026
CryptoGuide Exchange is an independent research and comparison platform, not an exchange, broker, custodian, investment adviser or legal adviser. This is educational research, not investment or legal advice.