The guided path: migrate with the AI skill
The guided path runs the migration through an AI skill in an agentic chat window. It is the fastest route and the one most teams should start with. On a clean starter project, the full run finishes in under fifteen minutes.
What you'll learn
How to start a guided migration
What the skill checks before it runs anything
What each step produces and how progress is reported
Where to find the artifacts when the run completes
Start the migration
Open your agentic chat window with the migration skill installed, and state what you want:
I want to migrate my Contentful space to Contentstack.The skill responds with the migration plan and begins by checking prerequisites. It confirms Node, the CLI, the plugin, your Contentstack login and region, and your Contentful login and accessible spaces. If anything is missing, it tells you exactly what to fix before continuing.
How the run proceeds
The skill works through the migration in order and shows progress at each step. It gates the steps that touch live accounts or modify your code, so it asks before it creates a stack and before it edits your repository. The sequence is:
Verify prerequisites and gather inputs such as the space ID and organization UID.
Confirm the migrate plugin is installed and current.
Run the content migration, which exports from Contentful, converts to a Contentstack bundle, creates a new stack, and imports the content.
Migrate the application code that reads from the CMS.
Show a completion summary with the new stack details and artifact locations.
After each step the skill surfaces the meaningful output, such as the exported entity counts and the new stack key, rather than a wall of logs.
What the content step does
The content step runs a single command under the hood that chains export, conversion, and import. The skill captures the resulting stack name, stack API key, region, bundle path, and credentials file, and carries them into the code migration so you do not re-enter them.
What the completion summary contains
When the run finishes, the skill reports the counts imported into the stack, the files it changed in your codebase, any field UIDs it had to guess, and any call sites it marked with a TODO(migration) comment for you to review. It also points you to the workspace directory holding the export, the bundle, the credentials, and the logs.
Key takeaways
Start the guided path by stating your migration intent in an agentic chat window.
The skill checks every prerequisite before it runs anything.
It gates stack creation and code edits behind explicit confirmation.
It captures the new stack credentials and carries them into the code migration.
The completion summary lists counts, changed files, guessed UIDs, and remaining TODOs.
Frequently asked questions
How do I start a guided migration with the AI skill?
Open the agentic chat window with the migration skill installed and state your intent (for example, migrating a Contentful space to Contentstack). The skill responds with a plan and begins prerequisite checks.
What prerequisites does the skill verify before running the migration?
It confirms Node, the CLI, the migrate plugin, your Contentstack login and region, and your Contentful login and accessible spaces. If something is missing, it stops and tells you what to fix.
What is the step-by-step sequence the guided run follows?
It verifies prerequisites and inputs, confirms the plugin version, migrates content (export, convert, create stack, import), migrates application code, then prints a completion summary with stack details and artifact locations.
What happens during the content migration step?
The skill runs a single chained command that exports from Contentful, converts to a Contentstack bundle, creates a new stack, and imports content. It captures stack details and paths for use in the code migration.
What does the completion summary include and where are artifacts stored?
It reports imported counts, changed files, any guessed field UIDs, and any TODO(migration) call sites to review. It also points to a workspace directory containing the export, bundle, credentials, and logs.