You lose unnecessarily a lot of time, you waste a lot of money unnecessarily or you get a huge drop in visitor numbers. These are just three pitfalls of a content migration. If it’s up to me, don’t fall for that. In this article I share seven tips for a successful content migration.
- 1. Align planning and availability of all departments
- 2. Know your stakeholders and involve them in time
- 3. Start with a well-prepared kick-off
- 4. Draw up a clear content governance
- 5. Don’t forget to test
- 6. Start the transfer on time
- 7. Implement a content lifecycle
1. Align planning and availability of all departments
Every content migration is a collaboration between multiple departments or external parties. It is almost always the next three parties.
- The business. Usually the marketing, e-commerce or other department that is responsible for the commercial side of the website.
- The content team. The content managers and web editors who manage the content on the site. They usually work in a CMS . Content ensures that all pages are findable, current, working properly and according to the corporate identity.
- Development. The more technical people like programmers and UX designers who translate the designs of your new site into code, components and page structures. They often set up your new CMS.
Watch out for dependencies
Each department has its own planning and responsibilities in the Canadian CTO CIO Email Lists project. To avoid delays or delays, it is important that you coordinate the planning and priorities with the three departments. Pay close attention to the dependencies on each other.
For example, a logical sequence is:
- The content team will fill the pages between August 1 and 31.
- The business provides feedback between August 21 and September 14.
- Development fixes the bugs that bring content and business between September 1 and 30.
With such a jointly coordinated planning, every department knows when people need to be available.
2. Know your stakeholders and involve them in time
Every organization has multiple stakeholders: people or departments that are directly or indirectly involved in the project. At the start of your project, make an inventory of who the stakeholders of the content migration are. And know their role:
- Are they responsible for the content, the budget, the planning or the people?
- Do you only have to inform them or are they also (co-)decision-makers?