migrate-objects

Migrate Objects

Prerequisite: Support Level Check

Check support from the configure() response.

If support is basic, load BASIC_SUPPORT.md and STOP. Do not continue with the steps below.

On Entry IMPORTANT DO NOT SKIP

Tell the user:

Phase 2: Migrate Objects. Now we'll deploy your objects to Snowflake according to your wave plan (if you created one in assessments). Each object goes through a deploy-test-fix loop.

Step 1: Confirm setup is finished

The Snowflake target (connection + database) and the testing path are configured by the setup state machine, not here — they're the last steps of setup, gated behind the post-assessment continueToMigration prompt. A user who stopped at assessment has none of them yet.

Call progress_setup().

• completed: true → setup is finished; continue to Step 2.
• Anything else (a next_task / next_prompt came back) → setup isn't done. Load ../setup/SKILL.md and drive it to completion, then come back. Don't ask for a connection, database, or testing preference yourself — the machine owns those questions and persists the answers.

This is also the path for a user who answered "Not now" at the gate and has since changed their mind: the prompt is re-offered, and answering "Yes" walks them through the Snowflake target and testing setup.

Advancing and reporting

This rule is the same for every task in the loop below — deploy, test, capture, seed, fix, validate:

1. Do the task's work as its skill describes.
2. Ask what's next. Re-pull migration_status(mode="my_objects_summary") (or migration_status(mode="next_task", object_id="<id>") for one object). The machine advances you when it can see the work is done — a tool wrote the registry field, the object exists in Snowflake, or the expected file exists.
3. Call transition_status to report or override:
   • a failure you can't fix — transition_status(status='advance', task='<task>', outcome='failed', error='<sql|infra>');
   • an outcome the system can't observe and you had to judge — e.g. "all tests passed" (migrate-object/RUN_TESTS.md), view parity (migrate-object/VALIDATE_VIEW.md), ETL stabilization (migrate-etl/SKILL.md);
   • an override — bypass a precondition, reset an errored task, or skip.