Nourish commerce / ivory, folk petals & coral

An ecommerce replatforming proposal for a store moving from WooCommerce to Shopify. It covers what the current store costs to run, the recommendation, the four parts of the migration, what is included, a 14-week timeline, the team, a similar store’s results and three fixed-price options.

Ecommerce Replatforming Proposal

<h2 style="font-family:var(--proposal-font-heading);font-size:clamp(30px,4.2cqw,48px);line-height:1.12">Introduction</h2>

Introduction

<h2 style="font-family:var(--proposal-font-heading);font-size:clamp(30px,4.2cqw,48px);line-height:1.12">Your situation</h2>

<p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5;color:var(--proposal-heading)">Hosting, security patches, extension licences and developer hours, from the invoices you shared. If anything has changed, let us know.</p>

What your current store costs to run each year, thousand USD

<p>Hosting, security patches and extension licences on your current platform take a growing share of your budget, and upgrades break your customisations.</p>

Your platform costs more each year

<p>Landing pages, promotions and collection changes go through a developer queue, so your campaigns launch later than you plan them.</p>

Your team waits for developers

<p>You have years of products, customer accounts, order history and ranked URLs. Losing any of them would cost you sales and support time.</p>

Your data must arrive intact

Your situation

<h2 style="font-family:var(--proposal-font-heading);font-size:clamp(30px,4.2cqw,48px);line-height:1.12">Our recommendation</h2><p style="font-family:var(--proposal-font-heading);font-size:30px;line-height:1.3">Rebuild your store on the new platform, rehearse the data migration twice, and switch over in one planned overnight window in week 14.</p>

<p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5;color:var(--proposal-heading)">You get your catalog, customer accounts and order history mapped field by field, a rebuilt {{NEW_PLATFORM}} store your team can run without a developer, a redirect for every indexed URL, and counts that show your data arrived complete.</p>

<p><strong>What the project includes</strong></p>

Our recommendation

<h2 style="font-family:var(--proposal-font-heading);font-size:clamp(30px,4.2cqw,48px);line-height:1.12">How the migration works</h2>

<p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5;color:var(--proposal-heading)">The move has four parts. You approve each one before the next begins.</p>

<h3>Every field has a destination</h3><p>Your products, variants, collections, customer accounts and order history are listed field by field, with where each one goes on the new platform and what happens to fields that have no direct match.</p><ul><li>Field map for catalog, customers and orders</li><li>Decisions on custom attributes and metafields</li><li>Migration plan you sign off</li></ul>

Data mapping

<h3>Your store, rebuilt for the new platform</h3><p>Your theme, product and collection pages, cart and checkout are rebuilt to your current design standards, and your payment, shipping, tax, email and ERP connections are set up on apps or native features.</p><ul><li>Theme built from your brand guidelines</li><li>Payments, shipping and tax configured</li><li>Up to 12 apps and integrations set up</li></ul>

Store rebuild

<h3>Two full practice runs</h3><p>Your full data set is migrated twice into a test store. After each run your team checks samples of products, customers and orders, places test orders and reports anything wrong before the live run.</p><ul><li>Record counts compared after each run</li><li>Sample checks signed off by your team</li><li>Timed run to set the cutover window</li></ul>

Rehearsals

<h3>One planned switch-over night</h3><p>Your old store goes into maintenance mode, the final orders and customers since the last rehearsal are moved, your domain is pointed at the new store and redirects go live. Checkout is checked with real payments before your store reopens.</p><ul><li>301 redirects for every indexed URL</li><li>Rollback plan agreed in advance</li><li>Reconciliation report the next morning</li></ul>

Cutover

How the migration works

<h2 style="font-family:var(--proposal-font-heading);font-size:clamp(30px,4.2cqw,48px);line-height:1.12">What is included</h2>

<p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5;color:var(--proposal-heading)">What the recommended option covers, and what it does not.</p>

Field map and migration plan

Theme and store rebuild

Up to 12 apps and integrations

Two full data rehearsals

Redirects for every indexed URL

Cutover night and reconciliation report

Cleaning or de-duplicating historical data

A guarantee of zero downtime

Platform, app and payment fees

What is included

<h2 style="font-family:var(--proposal-font-heading);font-size:clamp(30px,4.2cqw,48px);line-height:1.12">Timeline</h2>

<p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5;color:var(--proposal-heading)">Work starts on {{KICKOFF_DATE}}. Each stage ends with your sign-off before the next one starts. We avoid cutover during your peak trading weeks.</p>

<p>Data audit, field map, URL inventory, app list and the migration plan.</p>

Map and plan

<p>Theme, pages, checkout, apps and integrations, reviewed on a private test store.</p>

Rebuild

<p>Two full data migrations into the test store, with counts and sample checks after each.</p>

Rehearse

<p>Redirects loaded, final data moved on the agreed night, checkout checked and counts reconciled.</p>

Cut over and reconcile

Timeline

<h2 style="font-family:var(--proposal-font-heading);font-size:clamp(30px,4.2cqw,48px);line-height:1.12">Client results</h2>

<p>A recent engagement with a similar brief, and what it delivered.</p>

Client results

<p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5;color:var(--proposal-heading)">{{SELLER_NAME}} is your main contact. The same three people work on your migration from kickoff to the reconciliation report.</p>

<p>Owns the plan, the schedule and the cutover runbook, and leads the switch-over night.</p>

Migration lead

<p>Builds the field map, runs both rehearsals and the live migration, and writes the reconciliation report.</p>

Data engineer

<p>Rebuilds your theme and checkout, sets up apps and integrations, and loads the redirects.</p>

Store developer

Your team

<h2 style="font-family:var(--proposal-font-heading);font-size:clamp(30px,4.2cqw,48px);line-height:1.12">Pricing</h2>

<p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5;color:var(--proposal-heading)">Three fixed-price options. We recommend Migrate and rebuild.</p>

<p>Prices are in USD and exclude tax. Each option is paid in three parts: 30% on approval, 40% when you sign off the test store and 30% when you sign off the reconciliation report.</p>

Your data moved safely. Your own team or theme partner builds the store.

Migrate

The data, plus a rebuilt store your team can run without a developer.

Migrate and rebuild

Plus three months of help while your team settles in.

Migrate, rebuild and support

<h3 style=";font-family:var(--proposal-font-heading)">Included in every option</h3><ul><li>A fixed price agreed before work starts</li><li>Two full rehearsals before cutover</li><li>A rollback plan agreed in advance</li><li>You own the store, theme and data</li></ul>

<p>Platform, app and payment provider fees are billed to your accounts directly. This proposal is valid until {{VALID_UNTIL}}.</p>

Pricing

<h2 style="font-family:var(--proposal-font-heading);font-size:clamp(30px,4.2cqw,48px);line-height:1.12">Questions</h2>

Questions

<h2 style="font-family:var(--proposal-font-heading);font-size:clamp(30px,4.2cqw,48px);line-height:1.12">Next steps</h2>

<p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5;color:var(--proposal-heading)">How we get started.</p>

<p>Accept on this page, or reply to this email. We send the first invoice for 30%.</p>

Approve the migration

<p>Within five working days we meet your team and collect admin access to your store, hosting and domain.</p>

Kickoff and access

<p>By the end of week three you review the field map, the URL inventory and a proposed cutover date.</p>

Ecommerce Replatforming Proposal - Preview