Square Pre-Migration Preparation Checklist

Preparing for Square starts with the unit actually sold: an Item family, its Item Variations, and the location and channel in which each variation is available. An optional purchase choice, a positive stock count, and an online listing describe different parts of that model.

Square preparation should begin by defining how the Target Store will use Square Catalog, locations, inventory, Customer Directory, Orders, payments context, fulfillment, Square Online, and connected applications. Square represents a Product family as a Catalog Item and its sellable units as Item Variations; modifiers, Categories, custom attributes, taxes, discounts, and locations remain separate relationships.

A useful preparation package records the action, owner, evidence, and ready condition for each major area. This prevents a source Product option from being misclassified as a Square modifier, a location-specific stock quantity from being reduced to one total, or historical payment evidence from being confused with current Square payment configuration.

Confirm the Square Operating Model and Location Scope

Define whether Square will support point-of-sale activity, Square Online, one or several physical locations, warehouses, services, delivery, pickup, shipping, or external fulfillment. Record the intended merchant account, region, enabled Square products, application permissions, and location assignments needed by that model. Collect records from the actual Source Store separately; choosing Square does not establish that every required destination feature or data path is available.

The operating model is ready when every location and channel has a purpose, every inventory source has an owner, and Square Online requirements are separated from Catalog records.

Prepare Access, Source Archives, and Control Evidence

Collect:

• source administrator access and required Square Dashboard permissions;
• access to Catalog, Items, modifiers, Categories, locations, inventory, Customers, Orders, Square Online, and connected applications;
• dated exports or backups for Products, Customers, Orders, content, media, discounts, taxes, and custom data;
• location, inventory, and fulfillment reports;
• application exports and external-system documentation;
• external Product, variation, Customer, Order, and location identifiers;
• a source-change owner for catalog, Customer, Order, content, and stock updates during the migration window.

If a source system cannot provide an export, record the affected records, evidence alternative, accountable owner, and readiness decision. Protect dated archives and credentials, record their coverage and recovery owner, and retain original Product, variation, modifier, location, Customer, Order, and external identifiers before approved cleanup. Keep any normalization in a traceable change ledger so source values remain recoverable.

Prepare Catalog Items, Item Variations, Options, and Modifiers

Square Catalog separates Items, Item Variations, Item Options, modifiers, Categories, discounts, taxes, images, units, and custom attributes. Prepare representative source patterns that expose those distinctions.

Include:

• simple Products that will become one Item with one Item Variation;
• Products with size, color, style, or other variation dimensions;
• Item Variation SKU, barcode, price, unit, image, and stock relationships;
• reusable Item Options and inconsistent legacy variation names;
• list-based and text-based modifier requirements;
• Products with taxes, discounts, units of measure, or custom attributes;
• services, digital entitlements, subscriptions, bundles, or application-owned behavior;
• ERP, warehouse, marketplace, supplier, and accounting identifiers.

Prepare the actual modifier-list definitions and Item assignments, including list-level or Item-level selection rules, individual overrides, defaults, and online or receipt display requirements. List modifiers can add a price; text modifiers collect input and cannot carry their own modifier price, so any charge needs an explicitly prepared Item or other commercial owner. Preserve reusable option definitions and the real combination-to-variation relationship rather than inferring stock units from labels.

The Catalog area is ready when every major Product family has a defined Item, Item Variation, Item Option, modifier, tax, discount, Category, and identifier treatment where relevant.

Prepare Categories, Images, Taxes, Discounts, and Custom Attributes

Prepare Catalog relationships beyond Items and variations:

• Category hierarchy or Product grouping;
• images associated with Items, Item Variations, or Categories;
• taxes and Product tax assignments;
• discounts, pricing rules, and historical promotion context;
• measurement units and quantity precision;
• custom attribute definitions and values;
• source visibility or channel flags;
• Square Online Product and Category relationships.

Do not reduce these objects to Product text. Their relationships can affect checkout, reporting, search, inventory, and external integrations. When the selected Square model uses different sellable and stockable units, preserve the original measurement definitions and conversion rule with the affected variations. Do not assume that one unit sold always removes one unit stocked, or that every account and compatible workflow exposes the same unit model.

Prepare Locations, Inventory Counts, and Stock Authority

Square inventory is calculated for Item Variations at locations. Current Inventory API evidence can include counts, physical counts, adjustments, and states such as in stock, sold, returned, received, or waste. For current cross-location stock movement, the Inventory API represents the movement as an adjustment with from/to locations rather than the retired TRANSFER change representation. This inventory-change model is separate from any managed transfer-order workflow.

Prepare:

• every source warehouse, store, branch, supplier pool, or fulfillment location;
• the intended Square location for each source stock pool;
• Item Variation and location identifiers;
• current counts and the timestamp they represent;
• reserved, damaged, returned, in-transit, or other source states;
• external inventory authority and synchronization keys;
• opening physical counts and source-change ownership.

Prepare computed counts and physical-count evidence with their stock state, location, unit, and timestamp. Manual sold-out status can be set independently of inventory tracking and quantity, so retain the actual variation or modifier availability overrides and channel context separately. Opening stock, pending sales or fulfillment obligations, and historical adjustments need distinct evidence to prevent the same quantity being accounted for twice.

The area is ready when every stock quantity has one Item Variation, one location, one timestamp, one quantity meaning, and one authoritative owner, with availability and approved consolidation decisions recorded.

Prepare Customer Profiles, Groups, Segments, and External Identity

Square Customer profiles can contain contact details, company information, addresses, reference IDs, notes, groups, segments, marketing preferences, and custom attributes. Prepare identity records according to their actual business role.

Include:

• registered and guest buyers;
• duplicate email or phone examples;
• Customer groups and segment relationships;
• company or organization context;
• marketing preferences and consent evidence;
• loyalty, gift card, membership, or subscription relationships;
• CRM, ERP, marketplace, and accounting identifiers;
• Order relationships and historical addresses.

Authentication, stored payment methods, loyalty ledgers, and specialized application profiles require separate owners. A Square Customer profile does not automatically reproduce those relationships. Confirm account access for the exact Source-to-Square path, including verification, supported sign-in or reset/activation handling, first-login expectations, and Customer communications. Record the owner and approved treatment for payment tokens, balances, or application records that the selected path does not carry.

Prepare Historical Orders, Payments, Fulfillment, and Returns

Select Orders that expose Item Variations, modifiers, custom line items, taxes, discounts, service charges, tips, Customer references, location, source, fulfillment, payments, refunds, and external IDs.

Historical Orders preserve past sales and returns, including original line descriptions, prices, taxes, discounts, tenders, dates, and location context. Current payment activation, devices, POS settings, shipping, delivery, pickup, taxes, staff permissions, and notification behavior remain separate Square configuration. Prepare how historical imports will be kept from initiating new payments, stock changes, fulfillment, Customer emails, or connected-application events; retaining history does not authorize replaying those actions.

Prepare Square Online Content, Domains, Navigation, and URLs

When Square Online is in scope, prepare:

• Product and Category online visibility;
• Square Online pages, policy content, Blog or editorial content where applicable;
• navigation, footer links, campaign landing pages, and internal links;
• Product, Category, page, and campaign URLs;
• metadata, images, canonical relationships, and redirects;
• domain ownership and cutover dependencies;
• pickup, delivery, shipping, and location relationships shown online;
• embedded forms, widgets, scripts, and application content.

Square Catalog data alone does not recreate Square Online page structure or navigation. Those records require separate evidence and owners.

Inventory Applications, APIs, and External Systems

Create a dependency register for every Square application, source extension, API, webhook, automation, marketplace, ERP, PIM, WMS, CRM, accounting, tax, shipping, loyalty, subscription, booking, delivery, analytics, and reporting system.

For each dependency, record:

• business purpose;
• Catalog Items, Item Variations, Customers, Orders, locations, inventory, or content affected;
• authoritative system and external IDs;
• export or API availability;
• configuration and credentials owner;
• continuing destination, replacement, or retirement decision;
• evidence required before the destination workflow is configured.

The register is ready when every active custom attribute, listing ID, loyalty value, stock key, or Order reference has a named owner and parent Square object.

Select Representative Migration Test Samples

For every sample, record the source ID, source URL where relevant, business reason, original values and relationships, intended Square representation, location, external keys, approved exclusions, and responsible reviewer. Include quantity-versus-availability and unit-conversion cases where the operating model uses them. The packet should state what is expected to be represented before the representative migration test begins.

Complete the Square Readiness Gate

The preparation gate is complete when no critical Catalog Item, Item Variation, modifier, location, inventory, Customer, Order, Square Online, or integration decision depends on an undocumented assumption. Each required gap must be resolved, excluded with approval, or kept on hold; an owner and a due date alone do not make the inputs ready.

Conclusion

Square preparation should produce a location-aware commerce evidence package. Catalog Items must be connected to their Item Variations, Item Options, modifiers, Categories, taxes, discounts, and custom attributes. Inventory must remain attached to the correct variation and location, Customers and Orders must preserve their historical relationships, and Square Online or application records must have named owners.

When those decisions are documented before the representative migration test, the sample set can reflect the intended Square operating model without confusing historical commerce data with current POS, payment, fulfillment, or online configuration.

Common Questions