How to maintain the information of new and old entities after the project name change?
This article introduces the data migration and maintenance process after the renaming of a Web3 project, covering official association explanations, duplicate entry handling, and multi-channel information synchronization to maintain consistency in brand entity information.
First publish the official association statement
After renaming, brand upgrading, or entity adjustment, a formal announcement should be published on the official website and official social media, clearly stating the old name, new name, effective date, old and new domain names, and the relationship of official accounts. This statement is an important source for updating information on third-party pages in the future.
Do not rush to create duplicate entries
When there is already a data page for the project, prioritize submitting the renaming, former names, and official association proof to avoid having multiple independent project files existing simultaneously. Only consider submitting new project information when it is confirmed that there are no existing corresponding entities.
Synchronously migrate key pages
The official website should set up a redirect from the old domain to the new domain, update documents and social media with the new name; data platforms and partner data pages should also submit corrections synchronously. Historical media reports may not be rewritten, but the current version can be provided through an official information summary page.
Observe consistency rather than pursuing immediate results
Search engines and AI systems may take time to re-understand the relationship between the old and new names. What the project party can control is the continuous provision of consistent, verifiable official information, rather than guaranteeing that a platform will immediately complete the entity merger.
Next steps
Modify information:
https://www.rootdata.com/projects/submit?ft=modifi
Create project:
https://www.rootdata.com/projects/submit?ft=create
RootData Boost:



