Migrate your content
With a Kontent.ai project set up and your audited content properly mapped, you can begin with the migration.We recommend you start with small migrations and continuously verify that the migrated content was imported correctly to avoid any surprises, such as missing content.
Migration recommendations
- Plan ahead. Coordinate a designated migration maintenance window with relevant stakeholders. Halt work in the CMS during this window to allow for the import process. You can also use the maintenance window to halt work in Kontent.ai or in your existing CMS to allow for creating a fresh data export.
- Use environments. When you’re starting with the migrations and testing your mapping logic, it’s best to create a new test environment for each time you want to import your mapped content. Once you trust your mapping logic, it’s fine to perform multiple imports into a single environment. The Migration toolkit doesn’t create duplicates.
- Start small. Test small-scale migrations in a controlled environment to ensure successful migration and alignment with your content and assembly model standards.
- Verify. Follow up with thorough quality assurance and testing to verify that the migration was successful and meets your content standards.
Import mapped data into Kontent.ai
Write migration logic to import your core content—the essential content needed for your business goals. Then follow with the rest of your content.What’s next?
Sign in with your Kontent.ai credentials or sign up for free to unlock the full lesson, track your progress, and access exclusive expert insights and tips!