Menu
Shopify projects go over budget in predictable places: the app that almost does what you need, the ERP sync nobody specified, and the redirects left until launch week. We scope those first, so the estimate is based on your store rather than a template.
What you get
A written project scope covering theme approach, the app stack and what should be custom instead, integrations, data migration, and URL and SEO continuity, with an estimate range for each phase.
A written scope, not a sales proposal. This is the structure every scope follows, with example values in place of your data.
| Checked | Example finding | Rating |
|---|---|---|
| Theme approach recommended | customized Online Store 2.0 themeIncluded | Included |
| Apps planned | 14, of which 4 replaceableMedium | Medium |
| Integrations needing middleware | ERP and 3PLHigh | High |
| Customer accounts to migrate | activation invites requiredMedium | Medium |
| Checkout logic to rebuild | 2 rules, as Shopify FunctionsHigh | High |
| URLs crawled for redirect map | full crawl, not sitemapIncluded | Included |
| Estimate ranges | 5 phases, each estimatedIncluded | Included |
plus the app-by-app recommendation and the data mapping table
Example values shown. Your report contains findings from your own environment.
Whether an existing Online Store 2.0 theme, a customized theme, or a headless Hydrogen build fits your catalog and your team, and what each one costs to run after launch, not only to build.
Every app you plan to install, what it adds to page weight and monthly cost, and which ones should be a small custom app or a Shopify Function instead. App sprawl is one of the most common reasons Shopify stores get slow.
ERP, PIM, 3PL, tax, reviews and subscriptions: which have a native Shopify connector, which need middleware, and how products, customers and order history move across.
A redirect map built from a full crawl of your current site, structured data parity on products and collections, and a plan for the fixed /products/ and /collections/ URL structure Shopify enforces.
Plenty of successful stores run on standard Shopify plans, so Plus should be a decision about specific needs rather than about size. Plus tends to earn its cost when you need checkout customization beyond what the standard plans allow, several storefronts for different regions or brands under one organization, higher API limits because your ERP or inventory system syncs constantly, or wholesale and B2B features alongside retail. If none of those apply, the money is usually better spent on the build itself. Shopify moves features between plans from time to time, so check its current plan comparison before deciding, and treat any agency that recommends Plus without asking about these requirements with some caution. The scope states which plan fits your requirements and why, so the recommendation is written down and can be checked rather than taken on trust.
Yes. Products, variants, collections, customers and order history can all be moved, either through Shopify's import tools and migration apps or through a scripted migration when the catalog is large or messy. A few things do not move and are worth knowing about early. Customer passwords cannot be transferred because they are stored as one-way hashes, so existing customers are invited to activate their accounts on the new store. Custom checkout logic has to be rebuilt as apps or Shopify Functions. And every old URL needs a redirect, because Shopify fixes product and collection paths under /products/ and /collections/, which rarely match the old structure. Handled properly, none of this is a reason to delay a migration. Discovered late, each one becomes a launch-week emergency. The scope covers all three explicitly.
Less than most teams expect. For a store that already runs on Shopify, a collaborator account lets us review the theme, apps and settings without you sharing your own login. For a store on another platform, read access to the admin and an export of the product catalog is enough to start. Beyond that we need a list of the systems the store connects to, such as ERP, 3PL, tax, email and reviews, even if it is rough, and thirty minutes with whoever knows the odd parts of how the business runs, because that is where scope surprises come from. Analytics access helps us see which pages actually earn revenue, which shapes where effort goes. We do not need a formal brief or requirements document. Producing one is part of what the scope is for.
This page covers one specific engagement. The service page has the complete scope, process and technology list.