Preparation for a Shopify Plus destination environment starts with store-qualified ownership. Organization access, a shared Product master, and a company contact each describe different relationships; none establishes readiness in every store. Preserve the source store, entity identifiers, commercial context, and continuing owner before deciding what each destination store will receive.
Shopify Plus preparation should establish how organization-level governance, individual stores, B2B companies, Markets, catalogs, Products, Customers, Orders, content, apps, and external systems will relate before any migration run begins. Shopify Plus adds operating scale, but each store still owns its own data, settings, and storefront context.
A useful preparation package records the action, owner, evidence, and ready condition for each major decision. This prevents expansion-store boundaries, B2B company relationships, catalog pricing, regional URLs, or organization-level integrations from being inferred after sample data has already been migrated.
Confirm the Shopify Plus Operating Model
Identify the actual Source Platform and source-store boundaries separately from the intended Shopify organization. Record the contracted plan, store purposes, roles, Customer account models, enabled B2B and Markets features, compatible apps, licenses, and implementation owners. Define whether the architecture uses a blended store, separate B2B/D2C stores, regional expansion stores, employee/VIP stores, or another structure. Current B2B capabilities vary by plan; companies alone are not a Plus-only distinction. Direct company-location catalog assignment and advanced payment requirements need their actual plan and configuration evidence.
| Preparation area | Decision to record | Owner | Ready evidence |
|---|---|---|---|
| Organization structure | Main store, expansion stores, development stores, regional stores, B2B stores, and shared governance | Executive commerce owner | Organization and store-purpose map |
| Data ownership | Which Products, Customers, Orders, content, domains, and apps belong to each store | Store owners | Store-by-store data-scope matrix |
| B2B model | Blended or dedicated store, companies, company locations, contacts, catalogs, payment terms, and Markets | B2B owner | Company and catalog relationship map |
| International model | Markets, languages, currencies, domains, subfolders, duties, taxes, and regional content | International owner | Market and domain matrix |
| Integration model | ERP, PIM, WMS, CRM, marketplace, tax, shipping, payment, analytics, and automation ownership | Technical owner | Organization-wide dependency register |
Do not assume organization-level management automatically shares store data or grants all store permissions. Each destination store needs its own data, configuration, app/license, access, and synchronization ownership. Organization roles and store roles are different evidence; inspect the permission scope needed in each intended store.
Prepare Access, Store Inventories, and Recoverable Backups
Collect:
- source administrator access and required Shopify Plus organization/store permissions;
- a complete list of source stores, domains, business units, regions, and brands;
- dated exports for Products, Customers, Orders, collections, content, reviews, discounts, and other in-scope records;
- Product media files and source content archives;
- B2B company, company-location, contact, catalog, payment-term, and tax examples;
- Markets, domain, language, currency, and regional content lists;
- app, Flow, integration, API, and external-system inventories;
- Customer and Order external-ID reports;
- high-value URL, redirect, and internal-link inventories;
- a dated source snapshot and change owner for the migration window.
| Evidence item | Why it is needed | Ready condition |
|---|---|---|
| Organization/store inventory | Prevents data from being assigned to the wrong Shopify store | Every target store has a purpose and accountable owner |
| Access record | Confirms organization and store-level areas can be inspected | Required permissions are available |
| Export archive | Preserves a recoverable source state | Files open, carry an export date and coverage record, and have a protected recovery location and owner |
| B2B evidence packet | Explains company, location, contact, and catalog relationships | Representative B2B structures are documented |
| External-ID register | Protects organization-wide integration continuity | Each key is assigned to the correct store and entity level |
Preserve dated untouched exports, media, definitions, and original store-qualified IDs, handles, option values, reference targets, and external keys before normalization. Record archive coverage, protected location, recovery owner, and changes after capture. Keep approved source-to-intended changes separately. When an application or regional store cannot produce required evidence, record the gap, its owner, and whether the affected scope must be excluded or held.
Prepare Products, Variants, Catalog Governance, and Store Assignment
Prepare Product families using the same variant, metafield, metaobject, collection, and external-identifier discipline required for Shopify, while also documenting which store or market owns each record.
Include:
- simple and high-variant Products;
- Product families with store-specific availability or content;
- B2B-only or D2C-only Products;
- regional Product versions, regulated Products, or channel-specific assortments;
- bundles, subscriptions, preorders, personalization, and app-owned Product behavior;
- Products synchronized with ERP, PIM, WMS, marketplace, or supplier systems;
- structured specifications, compatibility records, documents, and reference content.
| Source behavior | Shopify Plus preparation decision | Evidence |
|---|---|---|
| Product is shared across stores | Decide whether records remain independent, are imported to several stores, or are governed externally | Store assignment, source IDs, and external master key |
| Choice creates sellable inventory | Define Product and variant ownership | Parent/variant IDs, SKUs, stock, prices, and images |
| B2B assortment differs from D2C | Define catalog, Market, and store visibility relationships | Product/company-location scenarios |
| Regional content differs | Define Market/store ownership for content, domain, language, and currency | Regional Product matrix |
| Structured information is reused | Define metafield, metaobject, content, or app owner | Field schema and continuing consumer |
| Product behavior is app-owned | Identify the replacement app or external system | App record examples and related Product IDs |
The area is ready when every major Product family has a destination store, Product/variant structure, visibility owner, and store-qualified external key. Capture typed metafield definitions, entity scope, metaobject entries and references, and the active theme/app/API consumer independently from displayed text. Shopify’s initial expansion-store data copy excludes reference and category metafields; it does not establish that those relationships are prepared for another migration workflow. Store copies also need their own configuration, applications, and file/reference ownership.
Prepare inventory by variant, destination store, location, quantity state, timestamp, tracking/fulfillment setting, and authoritative system. A common SKU does not establish shared quantities across stores. Preserve opening stock, pending obligations, and historical Order snapshots separately, with synchronization owners and safeguards against a second stock effect from imported history.
Prepare B2B Companies, Locations, Contacts, and Catalogs
Shopify B2B relationships should be prepared as connected records. A company is the parent organization; locations carry commercial context such as addresses, tax, pricing, payment terms, and checkout settings. Contacts require actual company/location buying permissions, not merely an email or Customer record. Preserve IDs, assignments, roles, and approved access expectations separately from profile data.
Prepare:
- company identity and external account IDs;
- company locations, addresses, tax IDs, exemptions, and regional context;
- contacts and their company/location relationships;
- payment terms, deposits, draft-order expectations, and checkout settings;
- catalogs, Product availability, price adjustments, fixed prices, quantity rules, and volume pricing;
- B2B Markets and direct company-location catalog assignments;
- blended-store or dedicated-store decisions;
- B2B Order-history examples.
| Preparation item | Owner | Ready evidence |
|---|---|---|
| Company structure | B2B operations | Company/location/contact matrix |
| Catalog assignment | Commercial owner | Catalog-to-Market or catalog-to-location matrix |
| Product visibility and pricing | Sales and merchandising | Representative Product/company examples |
| Tax and payment context | Finance and operations | Location-level tax, exemption, and terms examples |
| External identifiers | Integration owner | CRM, ERP, dealer, procurement, and accounting IDs |
Do not reduce B2B companies to Customer tags. Connect each representative buyer to the correct location, buying permissions, catalog eligibility, commercial rules, and external account. Record Market-based versus direct location assignments and overlapping catalogs in the eligible purchasing context; a catalog name or price alone is incomplete. Preserve historical B2B scope as transaction-time evidence. Do not assign old retail Orders to a company solely by matching email; any history reassignment needs an approved relationship decision.
Prepare Markets, Domains, Localization, and Store Boundaries
Map countries, regions, languages, currencies, domains, subdomains, subfolders, local content, taxes, duties, catalogs, and B2B groups to the intended Shopify Plus store and Market.
| Source scope | Preparation question | Ready evidence |
|---|---|---|
| Regional storefront | Is it a separate expansion store or a Market within one store? | Decision record and data-owner matrix |
| Localized Product or content | Which store and Market own the language and route? | Regional content matrix |
| B2B region | Which B2B Market, catalog, company locations, and currency apply? | Market/catalog/company relationship example |
| Domain or subfolder | Which target route owns the source path? | Domain and redirect ledger |
| Regional app or integration | Is the dependency store-specific or organization-wide? | Technical ownership record |
Prepare high-value Product, collection, CMS Page, Blog Post, policy, campaign, and localized URLs. Each route needs an intended destination or retirement decision.
Prepare Customers, Historical Orders, and Store-Level Ownership
Customer and Order records must be assigned to the correct Shopify store. Prepare duplicate Customers across stores, shared CRM identities, guest buyers, addresses, tags, loyalty, subscriptions, and B2B contacts. Record each store’s account model and exact Source-to-Target verification decision, SSO dependency, or reset, activation, or first-login handling, with identity and communication owners. Company-location buying access remains separate from login continuity.
Select Order examples covering:
- each target store, Market, currency, and important channel;
- B2C and B2B Orders;
- discounts, gift cards, store credit, duties, taxes, and shipping adjustments;
- partial fulfillment, multi-shipment, cancellation, and refund scenarios;
- subscriptions, bundles, customization, or app-owned line data;
- marketplace, ERP, WMS, accounting, support, or CRM references.
| Preparation item | Owner | Evidence | Ready condition |
|---|---|---|---|
| Customer store assignment | Customer operations | Cross-store identity examples | Retain-separate and deduplication rules are documented |
| Account access | Customer experience | Store account-model and chosen-path decision, identity owner, and returning-Customer communication plan | Each store has an accountable access owner |
| B2B contact context | B2B operations | Customer/company/location relationship and actual buying permissions | Contacts are not treated as unrelated retail Customers |
| Historical Orders | Support and finance | Store-specific Order packet | Transaction lines, statuses, refunds, and external keys are explained |
Historical Orders preserve past transactions, including store, buyer/company-location context, line choices, prices, tax, discounts, addresses, status meanings, and external references. They do not configure current payment, fulfillment, tax, or B2B checkout behavior. Identify Flow, webhook, notification, payment, stock, fulfillment, subscription, and B2B-access events that the import plan must contain, with owners and expected restoration behavior.
Inventory Apps, Flow Automations, Integrations, and Custom Data
Create a dependency register across the organization and identify whether each dependency is store-specific or shared.
Record:
- app or system name;
- store or organization scope;
- business purpose;
- Products, Customers, Orders, content, or configuration affected;
- custom fields, metafields, metaobjects, webhooks, or external IDs used;
- export or API availability;
- Flow automations and triggering data;
- continuing owner, replacement, or retirement decision.
Priority dependencies include ERP, PIM, WMS, CRM, subscriptions, bundles, B2B, loyalty, reviews, search, personalization, tax, shipping, payments, marketplaces, fraud, analytics, and consent systems.
The register is ready when each required record and automation has an accepted destination or retained-system treatment, compatible enabled consumers, license/configuration owners, and continuing synchronization responsibility in the correct store. An app installation list without its data, permissions, trigger relationships, and store scope is incomplete. Imported catalog records do not install applications or configure their live rules.
Select Representative Migration Test Samples
| Sample | Preparation purpose |
|---|---|
| Product shared across stores | Expose store assignment, external key, content, and inventory ownership |
| High-variant Product | Expose variant, media, stock, and integration relationships |
| B2B company with several locations | Expose company, location, contact, tax, payment, and catalog context |
| B2B catalog Product | Expose Product availability, fixed price, quantity rule, or volume pricing evidence |
| Market-specific Product or page | Expose domain, language, currency, and regional content scope |
| Cross-store Customer | Expose duplicate identity and account-access decisions |
| Complex B2B or B2C Order | Expose line data, totals, fulfillment, refunds, and external references |
| App-owned or automated record | Expose app, Flow, webhook, and target-owner dependencies |
For every sample, record the source store, original ID and values, source URL where relevant, business reason, target Shopify store, intended representation and owner, external identifiers, agreed exclusions, and responsible reviewer. Keep separate expectations when shared Products, B2B buying access, overlapping catalogs, location inventory, and regional content cannot be represented honestly by one sample. These inputs prepare later verification.
Complete the Shopify Plus Readiness Gate
| Readiness question | Required evidence | Ready condition |
|---|---|---|
| Is organization and store scope defined? | Organization/store map | Every target store has a purpose and owner |
| Are access and exports recoverable? | Access record and dated archive | Required source and destination areas are available |
| Are Product and B2B relationships prepared? | Product, company, location, and catalog matrices | Representative commercial structures are complete |
| Are Markets and URLs assigned? | Market/domain/route ledger | Priority regional routes have destinations |
| Are Customers and Orders assigned by store? | Identity rules and Order packet | Cross-store ownership is documented |
| Are apps and automations inventoried? | Dependency register | Every important dependency has a continuing owner |
| Are representative migration samples selected? | Sample ledger | Store, B2B, regional, and exception patterns are covered |
| Are open decisions controlled? | Decision log | Required gaps are resolved, excluded by agreement, or held; accepted noncritical exceptions have owners and recorded scope effects |
Preparation is complete when no critical store, B2B, Market, Product, Customer, Order, URL, or integration decision depends on an undocumented organization assumption. Required evidence and destination prerequisites must be resolved, excluded by agreement, or held before the affected scope proceeds. A named owner and future deadline alone cannot make a missing buying permission, reference, or store configuration ready.
Conclusion
Shopify Plus preparation should convert organization scale into explicit store-level ownership. Products, B2B companies, catalogs, Markets, Customers, Orders, content, apps, and external systems must each have a defined store, relationship, and accountable owner.
When those decisions are prepared before the representative migration test, the sample set can represent the intended Shopify Plus organization instead of exposing unresolved store boundaries after data has already been moved.
Common Questions
How is Shopify Plus preparation different from ordinary Shopify preparation?
It gives particular attention to contracted organization scope, expansion-store boundaries, cross-store governance, advanced commercial requirements, and enterprise integrations. B2B companies are not exclusively a Plus feature under current plans. Record the actual entitlement and configuration for direct company-location catalog assignment or other advanced requirements, and preserve explicit ownership in every store.
Should regional businesses use Markets or expansion stores?
Prepare evidence for brand, Catalog, legal, language, currency, domain, operations, and integration differences. Use that evidence to define whether the region belongs in one store with Markets or in a separate store.
How should B2B Customers be prepared?
Prepare companies, locations, contacts and buying permissions, tax details, payment terms, catalog eligibility, pricing, and external IDs as connected records. Keep login continuity and approved historical B2B scope separate. A contact profile or matching email alone does not establish location authorization.
What should be recorded for B2B catalogs?
Record Product membership, Market or company-location assignment, overall adjustments, fixed prices, quantity rules, volume pricing, and the commercial owner of each catalog.
How should Customers shared across several source stores be handled?
Document whether the accounts should remain separate, be consolidated through an external identity system, or be represented independently in each target store. Include Order ownership and consent context in the decision.
When is Shopify Plus preparation complete?
It is complete when store boundaries, B2B buying and catalog relationships, Markets, Product/Customer/Order scope, apps, routes, and samples have evidence and accepted owners, with required destination prerequisites confirmed. Resolve, explicitly exclude, or hold required gaps before proceeding; owner names alone are insufficient.
Does a Customer export prove that B2B buying permissions are prepared?
No. Prepare the company, location, contact assignment, actual buying permissions, eligible catalogs, and commercial rules. A Customer profile or shared email cannot establish those relationships. Keep login continuity and any approved historical Order reassignment as separate decisions.
Does organization access establish readiness in every destination store?
No. Organization and store permissions have different scopes, and each store has independent data, settings, applications, and configuration owners. Record the access, compatible enabled consumers, and synchronization responsibility required in every intended store.
Does copying an expansion-store catalog preserve reference metafields?
Shopify’s initial expansion-store data copy excludes reference and category metafields. Prepare definitions, referenced entries, store-qualified links, file ownership, and the intended consumer separately. That copy workflow does not determine the coverage of every other migration method; confirm the selected path’s actual contract.