Before you engage with the migration team, you must complete the following items. These are items you can do now with information that is available. This work should be done in Asciidoc. This work is applicable for all teams - not just teams who are have been informed they are next in the migration queue. Regardless of when your team is starting your migration, you are still required to complete the following items before engaging with the migration team.

Product docs team - prerequisites

• Product docs team - Evaluate your content reuse and record the findings in the ToolX: Content Reuse Assessment Worksheet
• Product docs team - Run the Vale dita compatibility assessment. This tool exposes issues in your repo that will prevent a clean migration.
• Product docs team - Make changes to your links based on the linking strategy updates.
  • Part 1
  • Part 2
• Product docs team - Perform a Content Quality Assessment. Pay special attention to the modular docs requirements. Your content will not migrate properly if it is not modularized using the correct templates.
• Product docs team - Begin planning a draft TOC ditamap based on a ContentX content improvement, a content journey and Jobs to Be Done. Update any Asciidoc content that needs improvement to align with the new TOC structure.
• Product docs team - Clean your repo before we move. Remove unused content from your repo.
• Product docs team - Designate a team leader. If your team has a DPM or CS, it might be the people in those roles. If your team is small, it may be the lead writer. 

Helpful tools and resources

• Training materials
• Modular documentation refresher class