# AI Shopify Migration Proposal: Scope Before You Quote

A client asks you to move a store to Shopify, but ‘move everything’ is not a scope. Use AI to turn the brief into a discovery-led proposal that distinguishes product data, theme work, URL redirects and the cutover. This is useful for freelancers serving local or international clients from India and Pakistan.

## Your brief

1. List the current platform, approximate product and variant counts, languages and sales channels. Mark counts as unverified until discovery. Supply a small redacted product example rather than a customer database.

   ____________________

2. Separate required work from options: catalogue import, theme adaptation, content migration, URL mapping, integrations and post-launch support. State what the client must provide and approve.

   ____________________

3. Record the proposed currency, milestone approval owner and launch time zone. Ask about platform-plan restrictions and third-party apps before promising a particular checkout or integration.

   ____________________

## Prompt

Draft a discovery-led Shopify migration proposal from these facts: source platform [platform], catalogue [count to verify], required languages [languages], integrations [list], launch window [window]. Output scope, exclusions, access needed, discovery questions, milestone evidence and optional work. Do not invent a fixed price, delivery date, supported payment gateway or checkout capability. Mark assumptions and require client approval before changing the live store.

## Illustrative example

Illustrative brief: a small apparel shop has 120 listed products, two size options and 18 old collection URLs. A useful proposal first verifies variants and image rights, then includes a catalogue sample import and redirect mapping for review. It leaves loyalty-app migration optional until export access is confirmed. The launch milestone requires the owner to approve catalogue checks and a store-specific checkout test; it does not promise that a test order proves every payment method works.

## Acceptance checks

- [ ] Can each scope line be traced to a supplied requirement, with theme customization and third-party app work explicitly separated?
- [ ] Does the proposal identify who approves product accuracy, redirects, shipping settings and the launch window, without exposing customer credentials?
- [ ] Are discovery findings allowed to change the final quote through an agreed approval step, rather than silently expanding the job?

Do not let AI quote ‘complete migration’ from a homepage link. Hidden variants, app data and unavailable export tools can change the job. Use a bounded discovery milestone and keep destructive changes outside the proposal until the owner approves them.

---

Brainbaby · https://brainbaby.ai/blog/ai-shopify-migration-proposal

CC BY 4.0 — https://creativecommons.org/licenses/by/4.0/