Shopify Plus Migration Statement of Work Template

Count everything. A deliverable a client cannot count is a deliverable a client can expand.

1. 2.1Configuration of one Shopify Plus store and one expansion store for the markets listed in Schedule A.
2. 2.2A theme built on Shopify's Dawn reference architecture with the 9 templates listed in Schedule B (home, collection, product, cart, search, blog, article, page, contact).
3. 2.3Migration of up to 4,000 products and their variants, 60,000 customer records and 24 months of order history from the source platform, using Matrixify or an equivalent tool.
4. 2.4A 301 redirect map for every product, collection and CMS URL indexed on the source platform at kickoff, up to 6,000 URLs.
5. 2.5Installation and configuration of the replacement apps listed in Schedule C, covering reviews, subscriptions, search and loyalty.
6. 2.6Shopify Flow automations for the 5 operational workflows listed in Schedule D.
7. 2.7Launch-day support for a 12-hour window and 30 days of post-launch defect fixes.

Name what the engagement does not include. These are the lines your PMs will cite most often.

1. 3.1Cleanup, deduplication, enrichment or rewriting of product data, descriptions or images.
2. 3.2Custom apps, private apps or checkout extensions not listed in Schedule C.
3. 3.3ERP, PIM, WMS or 3PL integration beyond the connector settings provided by the chosen app.
4. 3.4Migration of gift card balances, store credit or customer passwords (customers will reset passwords at first login).
5. 3.5SEO content strategy, new copywriting and photography.
6. 3.6Paid app subscription fees and Shopify Plus platform fees, which are billed to the client directly.

The theme includes two consolidated revision rounds on desktop and mobile designs before build, and one round on the staged build. Revisions are limited to layout, copy placement and styling within the approved templates. New templates or sections are changes.

Acceptance needs a measurable test and a window. Without both, delivery never formally ends.

1. 5.1A test order completes end to end for each payment method and shipping zone listed in Schedule A.
2. 5.2A sampled 5% of migrated products and customers match the source export on title, price, SKU, inventory and tags.
3. 5.3All mapped redirects return HTTP 301 to a live destination.
4. 5.4The client signs a launch readiness checklist. Launch counts as acceptance of the migrated data set.

Tie each dependency to a date so a late input has a known effect on the schedule.

1. 6.1The client provides full admin access to the source platform and a complete CSV export within five business days of kickoff.
2. 6.2Source product data is migrated as is. Field mapping is agreed once, in writing, before the first import.
3. 6.3The client chooses replacement apps from the options presented by the agency within three business days.
4. 6.4Content freeze on the source store begins 72 hours before launch.

Requests that add templates, apps, integrations, markets, record volume beyond the stated caps, or data cleanup are changes. The agency issues a change order within two business days naming the request, the Schedule it amends, estimated hours, cost and launch impact. Work starts after written approval. A request raised during content freeze moves the launch date unless the client approves an expedited change order.