Migrate your content | Kontent.ai Learn

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.

Once the import finishes, you’ll see new content items and assets in your Kontent.ai project. Feel free to re-run the import with the same data if you need to. The Migration toolkit imports assets and content items only if they don’t already exist.

What’s next?

Your migration went well, and your content now lives in Kontent.ai. Congrats!If you set up just the essentials in your project, now’s the time for the rest:

Add Web Spotlight into the mix. That means defining spaces and preview URLs for your content.
Set up roles for your colleagues. Connect the roles to workflow steps for a tight content creation process.
Invite others. Make sure to give each person the right permissions by using specific roles and collections.

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?

Your migration went well, and your content now lives in Kontent.ai. Congrats!If you set up just the essentials in your project, now’s the time for the rest:

Add Web Spotlight into the mix. That means defining spaces and preview URLs for your content.
Set up roles for your colleagues. Connect the roles to workflow steps for a tight content creation process.
Invite others. Make sure to give each person the right permissions by using specific roles and collections.

import { importAsync } from "@kontent-ai/migration-toolkit";

// Import content from the migration objects
await importAsync({
  data: {
    assets: migrationAssets,
    items: migrationItems,
  },
  environmentId: "KONTENT_AI_ENVIRONMENT_ID",
  apiKey: "MANAGEMENT_API_KEY",
});