Document note only. Field Ledger is not a tax firm, cloud reseller, dental office, or insurer. Read your own form and confirm it with the preparer, billing desk, carrier, or another licensed professional.
This token migration map streamlines cross-reference processes for crypto holders switching from legacy tickers to updated network-issued ticker identifiers. It eliminates mismatches between historical transaction logs and post-migration tax reporting documentation, aligning records for both on-chain and centralized exchange transaction tracking to reduce administrative friction during record audits. It is designed to be stored alongside existing crypto tax record folders, and can be uploaded to your Field Ledger if you use that platform for secure, encrypted record retention. All guidance on this page is for educational purposes only; you should consult your licensed tax preparer for questions specific to your reporting obligations.
Migration Map Folder Organization Rules for Historical Old Ticker Transaction Records
All records related to your token migration must be stored in a dedicated, password-protected folder separate from unrelated crypto or tax records to avoid cross-contamination during review. The folder must include four mandatory subfolders, with no mixed file types per subfolder to simplify retrieval: 1) Legacy Ticker Transaction Source Docs, which stores all pre-migration exchange statements, on-chain export CSVs, wallet signature receipts, and staking/liquidity pool balance records dated before the official migration cutoff; 2) Network Migration Official Notices, which stores dated screenshots of project governance vote results, public migration timeline announcements, verified new contract address postings, and official FAQs published by the issuing network team; 3) Mapping Confirmation Records, which stores exchange migration receipts, on-chain swap transaction hashes, wallet import confirmations, and pre-migration holding snapshots; 4) Adjustment Filing History, which stores all correction requests submitted to tax preparers, exchange support teams, or network administrators, along with response receipts and approval confirmations. All file names must follow a consistent YYYY-MM-DD_descriptor naming convention, for example 2024-03-10_legacy_ticker_coinbase_transaction_export.csv, so any reviewer can identify content and date without opening the file. Retain both digital encrypted copies and offline cold storage copies of all folder contents for the full record retention period recommended by your tax preparer.
Ticker Cross-Reference Column Layout Specifications for Side-by-Side Migration Tracking
The core of the migration map is a standardized cross-reference table that links all legacy ticker records to the new ticker, with no custom columns added without documented approval from your tax preparer. The required column layout is defined below:
| Column Name | Data Source | Required Field | Field Purpose | Notes |
|---|---|---|---|---|
| Legacy Ticker Symbol | Pre-migration exchange statements, on-chain export CSV, official network pre-migration announcements | Yes | Match all historical transactions to the original network identifier for consistent cost basis tracking | Do not use unofficial community ticker variants; only use the ticker listed on official network communications prior to the migration cutoff date |
| New Ticker Symbol | Post-migration network official documentation, post-migration exchange statements, verified blockchain explorer entries | Yes | Align historical records to the current on-chain and exchange-listed identifier for accurate tax and transaction reporting | Verify the contract address for the new ticker matches at least two independent verified blockchain explorer entries before input |
| Migration Cutoff Timestamp (UTC) | Official network migration announcement, published on the project’s verified website and social channels | Yes | Separate pre and post-migration transactions to avoid double-counting holdings or misaligning cost basis calculations | Illustrative example: 2024-03-15T14:00:00Z is a sample cutoff for reference only; use only the timestamp formally published by the issuing network |
| Conversion Ratio (Old to New) | Official network migration announcement, exchange migration confirmation receipt, on-chain swap transaction output | Yes | Adjust historical cost basis and holding amounts to match post-migration token supply changes and your personal post-swap balance | Confirm the ratio matches both network documentation and your personal wallet swap transaction output before finalizing the entry |
| Supporting Transaction Hash | On-chain swap transaction receipt, exchange migration confirmation email, network support swap confirmation | No (required only for adjustment submissions) | Provide verifiable proof of valid migration for tax preparer reviews, exchange support inquiries, or audit requests | Link to the corresponding full transaction receipt file stored in the Mapping Confirmation Records subfolder for easy access |
All entries must be populated in both a non-editable PDF and locked CSV copy of the table, stored in the root of your migration folder. Avoid manual edits to the master table; all changes must be tracked as formal adjustments stored in the Adjustment Filing History subfolder.
Manual Adjustment Form Submission Protocols for Incorrect Ticker Mapping Entries
If you identify an error in your cross-reference table (including mismatched tickers, incorrect conversion ratios, wrong cutoff timestamps, or misaligned holding counts), you must follow a formal submission process to ensure all relevant parties have consistent, verified records. First, gather all supporting documentation to validate the correction, including original source records, official network documentation that contradicts the existing entry, and any transaction receipts that confirm the correct data. Next, complete a standard manual adjustment form that includes the original incorrect entry, the corrected entry, a 1-sentence explanation of the error source, and attached copies of all supporting records. Submit the form first to your crypto tax preparer for their records, then to any relevant exchanges that have incorrect ticker mappings for your account, and if applicable, to the network support team to resolve on-chain record mismatches. Retain a signed and dated copy of the form, all supporting materials, and any response receipts in the Adjustment Filing History subfolder. Do not submit incomplete adjustments, as these will be rejected by most institutions and lead to delays in record corrections. This page cannot file adjustments on your behalf; you must work directly with your licensed preparer or exchange support team to submit changes that meet their requirements.
Pre-Migration Check Note Completion Steps for Registered Wallet Address Holders
All holders who store the legacy ticker in self-custody wallets must complete a pre-migration check note at least 72 hours before the published cutoff timestamp to reduce the risk of lost tokens or record mismatches. Follow these steps in order: Step 1: Export all historical transaction records for the legacy ticker from all self-custody wallets and centralized exchange accounts you hold the token in, save copies to the Legacy Ticker Transaction Source Docs subfolder, and cross-reference balances across all accounts to confirm no missing holdings. Step 2: Verify the published migration swap contract address against at least two independent verified blockchain explorers, record the address in your pre-migration note, and link a dated screenshot of the explorer verification to your Migration Confirmation Records subfolder. Step 3: Complete a pre-migration holding snapshot that lists the total amount of legacy tokens held across all addresses, signed with your wallet private key to create a verifiable proof of holdings pre-cutoff. If you use Field Ledger for record storage, you can attach the signed snapshot directly to your migration folder for secure retention. Step 4: If you have tokens staked or locked in a liquidity pool, request written confirmation from the pool operator or staking provider that they will handle the swap on your behalf, and save a copy of the confirmation to your folder. Step 5: Add a dated note to your folder confirming that you have completed all pre-migration checks, and include contact information for your tax preparer if they will be handling post-migration reporting for your holdings.
Rollout Phase Schedule Milestone Definitions for Full Ticker Migration Deployment
All token migrations follow a standard 5-phase rollout schedule, though exact timelines vary by network, so you must reference the official timeline published by the issuing project team for your specific migration. Milestone 1: Pre-Announcement Phase, the period between the official network governance vote approving the migration and the publication of the final migration timeline, during which you should begin organizing legacy transaction records and monitoring official network channels for updates. Milestone 2: Cutoff Preparation Phase, the 7-day window immediately before the migration cutoff date, during which you should complete all pre-migration check steps, export all required records, and confirm no pending transactions for the legacy ticker that will process after the cutoff. Milestone 3: Migration Execution Phase, the 24 to 72 hour window around the cutoff timestamp, during which the legacy token contract is frozen, swaps are processed, and the new ticker is deployed on-chain and listed on supporting exchanges; do not send or receive legacy tokens during this phase to avoid lost funds. Milestone 4: Post-Migration Verification Phase, the 30-day window after the cutoff, during which you should confirm your new token balances match your pre-migration snapshot adjusted for the conversion ratio, submit any missing swap requests to the network support team, and finalize your cross-reference mapping table for tax reporting. Milestone 5: Full Deployment Complete, reached when 99% of circulating legacy tokens have been swapped, the legacy contract is permanently disabled, and all supporting exchanges have fully transitioned to the new ticker for all transaction reporting. Mark all milestone dates for your migration in your personal calendar to avoid missing critical deadlines for manual swap submissions.
Save a copy of your finalized ticker migration cross-reference table to both your encrypted cloud storage and offline hardware drive within 24 hours of confirming your post-migration balance is correct.