Switching guide · Shopify

Moving from Shopify to 121 CRM: what to map, test and keep.

A useful decision about moving from Shopify begins with the real data flow, not a logo on an integrations page. This Shopify guide explains the documented method, practical setup or migration sequence, important limits and the acceptance checks a small business should complete before relying on it.

Subscribe to 121 CRM Seller, billing and cancellationRead the migration checklist

Customer Thread

A migration plan you can inspect

Illustrative example

Discover
Export and inventory the useful Shopify records.
Map
Define destination fields, stages, owners and exclusions.
Test
Import a representative sample without live communication.
Approve
Reconcile exceptions and make a human cutover decision.
Human decision

Fictional example using Alder & Field; supplier capability is documented, while account availability and 121 service scope still need agreement for each customer.

Fictional working example

Map the move from Shopify

This code-built Shopify demonstration makes records, permissions, handovers and checks visible without presenting a live customer account.

121 CRM · Migration mapping

Source fieldCRM fieldStatus

Company nameOrganisationMapped

Primary emailContact emailSampled

Free-text notesHistory notesReview

Legacy stageOpportunity stageDecision

12 mapped4 sampled3 decisions open

Illustrative exampleSample records and field names are fictional. A real migration needs source-specific reconciliation.

What the destination needs

Move the relationships, not just the rows.

A useful migration preserves the meaning of contacts, active work, ownership and next actions. It also records what cannot move cleanly and who decides the treatment.

Capability 01

Import and export

Moves supported records through structured files, with mapping and validation needed before relying on the result.

How it works: Stores or organises supported business data under configured fields, permissions and record rules.
Why use it: Supports controlled migration and operational extracts when the data is prepared and reconciled.
Plan for: The platform does not make imported, duplicated or incomplete data accurate without review. Bulk migration requires mapping and reconciliation; do not treat a completed import as proof of accuracy or reversibility.
Your team owns: A data owner must define the record model and resolve quality, ownership and access exceptions.

Capability 02

Custom fields

Adds structured fields to supported record types so a business can capture information it actually needs.

How it works: Stores or organises supported business data under configured fields, permissions and record rules.
Why use it: Replaces important notes and spreadsheet columns with searchable, reusable data.
Plan for: The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns: A data owner must define the record model and resolve quality, ownership and access exceptions.

Capability 03

Duplicate management

Uses account rules and review steps to reduce or resolve repeated contact records.

How it works: Stores or organises supported business data under configured fields, permissions and record rules.
Why use it: Keeps teams from following up with the same person through conflicting records.
Plan for: The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns: A data owner must define the record model and resolve quality, ownership and access exceptions.

Capability 04

Contacts

Stores a person or lead with contact details, activity, ownership and related records.

How it works: Stores or organises supported business data under configured fields, permissions and record rules.
Why use it: Gives a team one place to understand who a customer is and what has happened.
Plan for: The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns: A data owner must define the record model and resolve quality, ownership and access exceptions.

Capability 05

Opportunities

Represents a potential sale or deal linked to a contact, value, owner and pipeline position.

How it works: Tracks a potential deal, stage, owner or task using configured pipeline and record rules.
Why use it: Shows which customer conversations are active commercial work rather than general contacts.
Plan for: Pipeline position is only reliable when users and workflows update it consistently.
Your team owns: A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status.

Current documented route

What can leave Shopify, and in what form

The provider documentation reviewed on 11 October 2026 describes this route: Export customers and any relevant orders or products, then decide whether the CRM needs customer and order context rather than attempting to copy an entire store. Treat the Shopify method as a starting boundary, because permissions, editions and configured options can change the actual result.

What the current documentation supports

Shopify supports customer CSV export and separate exports for products and orders. For Shopify, this is a general supplier capability; it does not confirm availability or inclusion in a particular 121 customer account.

Another supported part of the documented scope

The native HighLevel Shopify connection documents selected historical import and ongoing sync options. For Shopify, this is a general supplier capability; it does not confirm availability or inclusion in a particular 121 customer account.

A practical business question

Which active customer relationships must remain useful after the move, and what source history is genuinely needed to support them? Answer that before asking for every available field.

Migration method

A controlled way to move from Shopify

Use a bounded, reversible Shopify test before any live change; this sequence is practical guidance, not a promise that 121 has access to either account or that every step is included in a 121 package.

1. Preserve the source

Keep an untouched source export and record when, by whom and under which permissions it was created. For Shopify, use the documented route rather than copying an on-screen view and assuming it is complete; apply that check to the documented Shopify route.

2. Map records and meaning

Map contacts, organisations, opportunities, owners, stages, consent and important dates separately. Give every source field a destination, transformation rule or deliberate exclusion; apply that check to the documented Shopify route.

3. Test an awkward sample

Use ordinary records alongside duplicates, missing identifiers, long text, unusual characters and linked opportunities. Import contacts before dependent opportunities and keep the test isolated from live messaging; apply that check to the documented Shopify route.

4. Reconcile before cutover

Compare source and destination counts, inspect relationships and exceptions, obtain user acceptance and define a stop or rollback decision before the live move; apply that check to the documented Shopify route.

Acceptance before reliance

Test the normal route and the failure route

The Shopify example shows a reviewable sequence with human approval, not an active connection or a guaranteed service entitlement.

121 CRM · Control responsibilities

Control questionOwnerNext check

Who can export customer data?CustomerConfirm

Who changes workflow permissions?Agreed scopeRecord

What happens at account closure?SharedDefine

Which suppliers process data?SharedCheck

Illustrative exampleIllustrative governance pattern. It does not assert that a specific technical control or certification is in place.

Fictional example

How Alder & Field could test the decision

Alder & Field is a property-maintenance business. Its fictional Shopify records and narrow acceptance test demonstrate the method without implying a live connection or customer result.

The operating need

The team needs current customers and open work to remain visible after leaving Shopify; it does not need to recreate every historical screen or automation.

The trial

Alder & Field exports a bounded set of current contacts and open work from Shopify. The team maps five required customer fields and one pipeline, imports twenty records, then reconciles the count, owners, stages and a sample of notes before deciding whether to continue.

The evidence

Alder & Field's reviewer keeps the Shopify source count, test input, mapped output, timestamps, owner, exception log and configured-permission evidence; a pass means this agreed scenario behaved as expected, not that every future scenario is guaranteed.

Human approval point

The decision

Alder & Field names an owner to accept, revise or reject the Shopify design; anything unexplained remains outside live use until it has a documented rule, monitoring route and human response.

Limits and responsibilities

What to check before relying on Shopify

Shopify documentation establishes general capability, not customer-specific availability, commercial inclusion or a 121 migration commitment; put those boundaries in the decision rather than small print after go-live.

What the connection or export does not solve

Customer CSV files are limited in size and store objects have different formats and relationships.

A second boundary to plan around

Themes, apps, settings, gift cards, analytics and many store behaviours are not recreated by CRM contact import.

Account and commercial boundary

Confirm the relevant HighLevel, Shopify and connector plans, permissions, usage charges and supplier terms in the customer's own accounts. This Shopify page does not claim that integration or migration work is included in the 121 subscription.

Human approval point

Live acceptance still required

Before live Shopify use, confirm an owned connection, run a representative test, reconcile results and record failure handling; no live account test was performed for this public guide, so those checks remain customer-specific implementation work.

Questions about this page

Useful answers, without the sales fog.

1. Can every Shopify record be moved automatically?

No. The documented source export and HighLevel import cover particular objects and fields. Activities, relationships, files, automations, configuration and history often need separate extraction, transformation, rebuilding or deliberate exclusion.

2. What should be tested before leaving Shopify?

Test a representative sample of contacts and open work, including duplicates, missing values, custom fields and linked opportunities. Reconcile counts and relationships, ask users to inspect the result and keep an agreed rollback or correction route.

3. Will 121 move all of our Shopify data as part of the subscription?

This page does not make that commitment. Migration scope, source access, data quality, volume, history, connected systems, testing and responsibilities must be assessed and agreed separately before work begins.

4. Should Shopify be closed as soon as the first import succeeds?

No. Keep a controlled source archive and a defined overlap or read-only period until reconciliation, user acceptance, communication checks and the cutover decision are complete.

Read all CRM questions

Continue the journey

Switch to 121 CRM Migration checklist Field-mapping worksheet From paper records

Delegate the work. Keep the human.

Ready to organise the customer journey?

Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.

Subscribe to 121 CRM Seller, billing and cancellationCompare pricing