Driving a migration with the CLI or an AI agent

Everything you do on a migration in the dashboard — looking at source data, adjusting mappings, starting and watching runs, and checking what was loaded — can also be done from a command-line tool called graftport. The tool is built to be handed to an AI coding agent so the agent can act as a migration engineer for you: it investigates your data, adapts the mappings to your requirements, proposes runs, watches them, and tells you when something looks wrong.

You stay in control of anything that changes your migration.

What the agent does on its own

The agent can do everything that doesn’t cost money without stopping to ask:

• Browse your migrations, resources, and mappings.
• Sample real source records (both the cleaned-up shape and the raw data from your old store).
• Edit a mapping, validate it against real records until every sampled record passes, and publish the new mapping version so it’s ready for the next run.
• Run a dry-run — the agent can ask Graftport to compute exactly what would be sent to Shopify, without actually sending it. That way it can read the result and tell you whether the migration is ready before you pay for a real run.
• Read run progress, group load errors so the biggest problem is obvious, and inspect what was actually loaded.

What always needs your approval

Anything that costs money on the platform or could destroy in-flight work is proposed, not performed. The agent composes the exact action and shows it to you; it runs only after you say yes:

• Starting a real run (anything that actually pushes to Shopify). You see a preview of exactly what it will do and the estimated cost.
• Cancelling a run.
• Retrying a failed record.

The agent is instructed never to skip this confirmation.

A “passing” run is not always a correct run

A run can finish green and still have migrated something subtly wrong — empty product descriptions, collapsed variants, prices that don’t add up. The agent is taught to inspect the loaded result against a per-resource checklist and report anything suspicious instead of declaring success on a green check alone. Treat its summary as a second pair of eyes, not a guarantee — review the result in Shopify before going live.

Getting started

Install the tool and sign in. auth login opens your browser, signs you in the usual way, and asks you to authorize the CLI on a single “Authorize Graftport CLI” screen. Nothing to copy and paste.

graftport auth login
graftport skill install

skill install drops an up-to-date instruction guide into your AI agent so it knows how to use every command and, importantly, when to stop and ask you. From there, tell your agent what you want — for example, “prepare the product migration so prices come from the tier price when the base price is missing” — and it will work the loop, pausing for your approval before any change.

If you are on a headless server with no browser, pass --no-browser to print the sign-in URL so you can open it on another device, or --access-token <jwt> if you already have a token from your dashboard session.

If you’d rather drive it yourself, run graftport --help; every command also has --help, and the dashboard does the same things through buttons.