A migration update follows the record you already have
Contract migration support aligns public token details after a contract change or rebrand. The first decision is whether an existing profile needs correction, a new listing is required, or both. We map each destination to the specific change rather than send one general notice.
| Route | When it fits | Typical focus |
|---|---|---|
| Existing tracker profile | The project already has a profile | Contract, ticker, name or logo details |
| New listing request | The destination does not have the required profile | Listing materials and the relevant platform route |
| DEX screener profile | A DEXTools or DEXScreener page needs an identity update | Approved token details and page-specific information |
For a new destination, CoinGecko listing coordination is distinct from changing an existing profile. The wider listings and verification overview can help your team separate these decisions. We confirm the route for each profile before preparing requests, leaving your team with a clear, considered map of the work.
One approved record keeps the change composed
A single reviewed record keeps the old and new token details connected throughout the update. Your named contact collects the contract addresses and chain names, final ticker and token name, logo files, official links, profile URLs and a concise explanation of the change.
Materials and proposed wording remain confidential within the coordination until you approve them for submission. We flag conflicting details instead of choosing between versions on your behalf. Your team confirms the facts and gives written sign-off on the prepared information; nothing leaves the desk before that approval.
A useful kickoff package identifies what has changed, what remains unchanged and which profiles matter. Include the current and replacement contract details, even when the rebrand is the primary concern. If an announcement already exists, provide its link so the wording can be checked against the approved details. A single person on your side should be available to confirm factual questions. This keeps requests precise and avoids revisiting the change history at each destination.
How are requests prepared for each platform?
We prepare each request around the profile and fields that your team has approved. The change is not treated as identical across CoinMarketCap, CoinGecko, DEXTools and DEXScreener; the destination map records what is being requested at each one.
CoinMarketCap and CoinGecko
For an existing profile, we connect the current project identity with the contract or brand change and prepare the supporting information for your approval. If circulating supply evidence is also relevant, we separate that work and coordinate it through circulating supply verification. A contract update alone is not treated as supply verification.
DEXTools and DEXScreener
We identify the affected token page and align the requested name, ticker, logo and contract details with the final project materials. Your team confirms that the replacement contract is the intended official asset before anything is submitted. For a correction limited to these pages, DEX screener profile updates may be the closer fit.
The destination record distinguishes a migration from a new listing or a displayed-profile correction. That distinction lets you approve the appropriate work for each platform.
The handover leaves a clear record
Your team receives a concise record of what was requested, what remains in progress and what is visible publicly. The materials are arranged for internal review and a straightforward handover, with one status kept current by your named contact.
- Destination map: affected profiles, requested fields and submission route.
- Approved project record: contract, ticker, name, logo and official links.
- Prepared requests: platform-specific information returned for your sign-off.
- Follow-up notes: responses received and any clarification requested.
- Evidence file: profile links and screenshots of visible changes.
The record separates submission from confirmed display, so a pending request is not presented as finished. If a block explorer also needs aligned token details, that can be coordinated as a separate item through explorer token information and logo updates. The agreed destinations and fields are listed before work proceeds. This gives your internal team a composed reference, including any project-side action still outstanding.
A note on platform decisions
A submitted request and a visible profile change are separate milestones.
CoinMarketCap and CoinGecko control their review and profile display; DEXTools and DEXScreener control how submitted details appear on their pages. We record submissions, replies and visible states separately, and do not describe a pending request as complete.
Your team can make the process easier to follow by providing final assets rather than draft alternatives, keeping public wording consistent with the approved contract details. Naming one person who can confirm facts. A migration announcement, profile request and project materials should describe the same change. If a separate new listing is needed, CoinMarketCap listing support can be considered alongside the profile work, with its purpose recorded separately.
Begin with the profiles that matter
A short change summary and the affected profile links are enough to establish the initial map. Include old and new contract addresses with their chain names, the approved ticker and token name, final logo files, official project links and any public explanation already available.
The coordination then follows five clear stages: scope the destinations, confirm the facts, prepare requests, coordinate submissions and record the visible outcome. Your team approves the factual details and public wording before requests proceed. A named contact keeps the status record current and directs follow-up questions to the person authorized to confirm project information.
If your team also needs a new listing or a separate profile correction, we can distinguish those items before the work begins. Supply verification is added only when it is genuinely part of the change. A short note naming the affected profiles is enough to begin; your named contact will prepare the destination map for your approval.
How it works
- 1. Share the changeProvide the old and new contract details, approved brand information and affected profile links. Name a team contact who can confirm project facts.
- 2. Map the destinationsWe list the requested fields and route for each profile, then flag missing or conflicting details for your decision.
- 3. Approve the recordYour team checks the consolidated details and prepared wording. Requests proceed only after your sign-off.
- 4. Coordinate and trackWe handle the agreed submissions, record platform responses and note any follow-up information needed from your team.
- 5. Receive the evidenceWe provide profile links, screenshots and a status record that distinguishes visible changes from pending items.
Frequently asked questions
Can a contract change and a new token identity be handled together?
Yes. We can coordinate both within one agreed scope once your team has confirmed the replacement contract, ticker, name and logo. The destination map shows which fields are requested for each profile, and your team approves the consolidated details before submissions are prepared.
Does a migrated token always need a new listing?
No. A migration may require an update to an existing profile, while a new listing is a separate request. We look at the current profile links and the change you are making, then record the appropriate route for each destination before any request is prepared.
What should we prepare for a CoinGecko identity update?
Have the existing profile link, old and new contract addresses with chain names, approved token name and ticker, final logo, official project links and a concise explanation ready. Mark any unsettled detail clearly. Your named contact will include confirmed information in the record and flag anything needing your approval.
Can the work be limited to DEXTools and DEXScreener?
Yes. The coordination can focus on those screener profiles without including CoinMarketCap or CoinGecko. Provide the affected page links and the fields to change; your named contact will map the requests and identify any materials or account contact details your team needs to provide.
How is timing established for migration coordination?
The sequence is mapped once your team can confirm the project details and provide final materials. At kickoff, we identify the destinations and project-side approvals required, then maintain a written status record. That record makes it clear which actions are complete and which are awaiting a platform response.
Can you promise a platform will display the change?
No. Each platform controls its own review and profile display, including whether and when a requested update appears. We commit to the agreed preparation, submission coordination, follow-up and reporting. The evidence file distinguishes a confirmed visible change from a request that remains pending.
Tell us about your project
Answer four quick questions and a manager will send you a plan, timing and a price range within the hour. Everything stays confidential.
Loading the form…