Sign in

Migration-Led Offer

Remove the switching cost first by making the move itself the offer the buyer is evaluating.

Pro involved Special Offer Structures

What it adds

The AI builder reads your onboarding runbooks, import tooling docs, and past transition notes to build a page whose entire argument is that leaving the current setup is safe and bounded. It converts because switching friction, not product preference, is what keeps dissatisfied buyers in place. The goal is to win displacement deals by making the transition plan the most detailed part of the pitch.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Read the supplied migration and tooling files and extract the real transition sequence: discovery, mapping, dry run, cutover, verification, and rollback.

  2. 2

    Publish that sequence as the page's primary content, with each stage stating who does the work, what the customer must supply, and how long it typically takes according to the runbook.

  3. 3

    Document what carries over and what does not. The "does not carry over" list is the credibility anchor and must be complete per the mapping spec, not softened.

  4. 4

    Describe the parallel-run and rollback options exactly as the runbook defines them, so the buyer sees a reversible path rather than a one-way door.

  5. 5

    Include a data-integrity verification step describing how the customer confirms the move succeeded, drawn from the verification procedure.

  6. 6

    Note continuity during transition — what remains operational and what has downtime — using only documented behavior, never an assumed zero-downtime claim.

  7. 7

    Define breakpoints: on mobile the transition sequence is a vertical stepper with per-stage detail collapsed and the carry-over list as a filterable two-tab view; on tablet the stepper is horizontal with detail beneath the active stage; on desktop the full sequence and the carry-over comparison render side by side without scrolling between them.

  8. 8

    Add an assisted-versus-self-serve selector if the source files document both paths, with the differences in scope and effort stated.

Edge cases it handles

5

The things an agent skips when you only say "build a migration-led offer".
  • Source systems vary widely; branch the transition plan by source type rather than presenting one generic path.
  • Some data cannot be migrated at all; state it in the does-not-carry-over list rather than describing a workaround as equivalence.
  • Contractual lock-in at the current provider; acknowledge it and describe timing options without offering legal advice.
  • A prior migration in the notes failed; use the documented remediation to strengthen the rollback section.
  • Volume beyond documented tooling limits; state the threshold and the alternate assisted path.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • The transition sequence is the page's primary content and matches the supplied runbook.
  • A complete "does not carry over" list is present and derives from the mapping spec.
  • Rollback and parallel-run options are described as documented.
  • Downtime and continuity statements reflect documented behavior with no assumed zero-downtime claim.
  • A verification step for confirming migration success is included.
  • Mobile, tablet, and desktop each expose every transition stage and the carry-over lists without truncation.
  • The builder reports which migration files it used and which timings or limits remain unverified.

Related offer files

How it works

  1. 1

    Copy the link

    Grab the Markdown blueprint URL for this offer type.

  2. 2

    Give it to your builder

    Paste it into Claude Code, Cursor, Codex, or whatever AI builder is already working in your app.

  3. 3

    It maps, then builds

    Your agent reads the blueprint first, then builds the offer into your app around the product, audience, and stack.

Works with your stack

These blueprints are written to adapt. They tell the agent to detect your framework, match your existing design system, and use your source files instead of guessing the offer.

Need it tighter than that? Customize the offer file and tell it exactly which source docs and stack to use.