How do customer tags and segments built up over years on the old platform migrate to Shopify's customer tagging and segmentation system?
Short answer
Customer tags migrate through Shopify's customer import file, in a comma-separated Tags column that Shopify treats as not case sensitive (Shopify Help Center, October 2026). Saved segments don't migrate: each is rebuilt as a query in ShopifyQL, Shopify's query language. Segments on spend or order count read only orders in Shopify, so they need migrated order history.
- Tags in the customer import
- One comma-separated Tags columnShopify treats tags as not case sensitive. Overwriting a customer replaces all its data, tags included, and of customers sharing an email or phone, only the last profile imports (October 2026).Source: Shopify Help Center (Importing and exporting customer lists)
- Metafields the import accepts
- Six types, each defined before importBoolean, Date, Date and time, Integer, Decimal and Single line text, in a column named customer.metafields.namespace.key (October 2026).Source: Shopify Help Center (Importing and exporting customer lists)
- Metafield types segments filter
- Date and time, number, text, true or falseCustomer segments can only be created from metafields of these data types, and only from customer metafields that have a definition (October 2026).Source: Shopify Help Center (Metafield-based customer segment filters)
- Segmenting by B2B company
- Shopify Plus onlyThe Companies filter is Plus-only, though business-to-business (B2B) selling runs on every plan, so tag wholesale buyers to segment them below Plus (October 2026).Sources: Shopify Help Center (Shopify-based customer segment filters, Shopify B2B features by plan)
Deploi’s call
Budget for the segment rebuild as a marketing workstream with a marketing owner, not as a line in the data-migration plan. It is query authoring and business-rule archaeology, and a data engineer is the wrong person to do it.
WaitRebuild in Shopify's native segments while
- The segment uses tags, spend, order dates, location or a recency, frequency and monetary (RFM) group, all built-in filters (Shopify Help Center, October 2026).
- Order history migrates too, because the import doesn't carry Total Spent or Total Orders (Shopify Help Center, October 2026).
- Native segments plus Klaviyo cover activation, which our segmentation record scores WAIT for most mid-market stores (October 2026).
CustomizeCarry the logic as tags or metafields when
- The segment is a hand-picked list: import it with a tag, and Shopify's import can build a segment from that tag (Shopify Help Center, October 2026).
- The segment filters on a custom field, which needs a metafield type segments read (Shopify Help Center, October 2026).
- You segment wholesale buyers below Shopify Plus, where the Companies filter isn't available (Shopify Help Center, October 2026).
Basis: Build or Buy Customer Segmentation & RFM on Shopify?, our Build vs. Buy decision record, scored WAIT.
How do customer tags move into Shopify?
Customer tags move into Shopify through the customer import file's Tags column, "A comma-separated list of tags used to tag the customer" (Shopify Help Center, October 2026). Tags are the cheap part of migrating a customer base's metadata, with three traps:
- Case variants match. Shopify says "Tags are not case sensitive", so Wholesale and wholesale count as one tag.
- Overwrites replace tags. Overwriting a customer with the same email or phone replaces "all of your customer data", import tags included.
- Duplicates go untagged. Customers with duplicate email addresses or phone numbers "are skipped during an import and aren't tagged", except the last profile that shares the email or phone, which Shopify imports.
The import offers to "Add tags to customers in this csv and use these tags to create a segment", so a hand-picked list survives the move as a tag-based segment. Import files can be no larger than 15 megabytes (Shopify Help Center, October 2026). Matrixify takes 2,000 customers per job on its $20 Basic plan, 20,000 on its $50 Big plan and unlimited on its $200 Enterprise plan, every 30 days (Matrixify pricing, October 2026).
Which legacy segments can you rebuild in Shopify?
Most legacy segments can be rebuilt in Shopify, but none imports: a Shopify segment is a ShopifyQL query that filters Shopify's own customer list (Shopify Help Center, October 2026). So each segment is rebuilt from its business rule.
| Legacy segment rule | Shopify filter | Rebuilds after migration? |
|---|---|---|
| Has tag X | customer_tags | Yes |
| Spent more than $X, or N orders | amount_spent, number_of_orders | Only with migrated orders |
| Ordered in the last N days | last_order_date | Only with migrated orders |
| Recency, frequency and monetary (RFM) tier | rfm_group, 11 groups | Only with migrated orders |
| Custom field equals a value | Customer metafield | Only four data types |
| Joined in the last N days | customer_added_date | No, it counts from the import |
| Words in the customer note | None | No, no filter reads notes |
| Wholesale company | companies | Shopify Plus only |
| Old-platform email opens or page views | Shopify Email and storefront events | No, only Shopify's own events |
Spend and order counts restart because the import's Total Spent and Total Orders columns "aren't imported with customer details" (Shopify Help Center, October 2026). Shopify's migration guide says to import "products first, then your customers, and then any historical orders" (Shopify Help Center, October 2026). So rebuild spend, order and RFM segments after the orders land.
Which metafield types keep a migrated customer field filterable?
Through Shopify's customer import file, a migrated customer field stays filterable only if it's a customer metafield of a type both the import and segments accept. The customer import takes six metafield types, each defined in the admin first (Shopify Help Center, October 2026). Segments can only be created from metafields of four data types: "date and time," "number," "text," and "true or false" (Shopify Help Center, October 2026).
| Import type | Segment data type | Filterable after import? |
|---|---|---|
| Single line text | Text | Yes |
| Integer or Decimal | Number | Yes |
| Boolean | True or false | Yes |
| Date and time | Date and time | Yes |
| Date | Not named in the segment list | Test it before you rely on it |
| Reference or rating | Not in either list | No |
So choose each metafield's type when you define it, before the first customer import, because that data-team choice decides months later whether marketing can filter on the field.
Which segments belong in your email platform, not Shopify?
Segments built on email engagement or browsing belong in your email service provider (ESP), because Shopify never held that history. Shopify's email and storefront event filters cover only events Shopify records, for the last 26 months (Shopify Help Center, October 2026). So opens tracked in Klaviyo or a legacy platform don't count. Those segments move, or fail to, between marketing tools, so scope them separately: why rebuilt email segments come out wrong.
Many legacy segments are also dead. In our judgment, years of accumulation leave one-campaign segments that nobody has opened since, and migrating them is work with no return.
In what order should tags and segments move to Shopify?
Tags and segments should move in six steps, with tags first, because most segment rebuilds depend on tags existing.
- Export every tag with a customer count. Tags on one or two customers are typos or one-offs, so clean them now, while cutover makes it cheap.
- Export every saved segment with its definition and last-used date. Retire anything untouched in twelve months, with the owner's name against the decision.
- Classify the survivors: rebuilds as a query, becomes a tag, becomes a metafield plus a query, or stays in the email platform.
- Define customer metafields before importing customers, choosing types that segments can filter.
- Import customers with their tags, then historical orders, in the order Shopify's migration guide sets (Shopify Help Center, October 2026).
- Rebuild the surviving segments and compare member counts against the legacy system before anyone sends a campaign to them.
When shouldn't you rebuild a segment in Shopify?
Don't rebuild a segment that has no audience, no data behind it or a better home.
Deploi’s point of view
Our own position, from building on Shopify. Kept apart from the sourced facts above.
- What we’ve seen
- The tag export is where the real discoveries happen. Free-text tagging over a decade produces the same concept spelled four ways, and nobody knows which spelling the automations depend on until one of them stops firing.
- Where we disagree
- Migration vendors quote "customers and segments" as one line item. Customers are a file transfer. Segments are a requirements exercise. Pricing them together produces an estimate that is too low and a scope argument in week four.
- What this page adds
- that a migrated attribute stays filterable only if it is imported as a metafield type that segments read, a choice the data workstream makes months before marketing builds on it, and that spend, order-count and RFM segments count only orders in Shopify because the customer import skips Total Spent and Total Orders.
Decision records behind this answer
When this answer changes
- Shopify adds metafield data types to segment filters, or list types to the customer import.
- Shopify opens the Companies segment filter to plans below Plus.
- Shopify starts importing Total Spent and Total Orders from the customer file.
- Shopify adds a way to import segment definitions or a created date for migrated customers.
- Shopify changes the 26-month window on its email and storefront event filters.
Related questions
This follows from How do wholesale/B2B customer net-terms payment history and credit-limit data migrate as customer metadata during a platform switch?
- What email marketing plugin functionality (from any platform) maps to Klaviyo, Attentive, or Postscript on Shopify, and what's typically lost in translation?
Email platform migrations carry contacts, unsubscribes and templates, not flows or segment logic, which are rebuilt in Klaviyo, Attentive or Postscript (Klaviyo Help Center, October 2026).
- Does blended B2B/DTC customer data (one person who buys both wholesale and retail) migrate correctly without duplicating or misclassifying the account on Shopify?
Blended customer data migrates correctly, without duplicates, only when each person becomes one Shopify customer before any company link.
Sources
Every figure on this page traces to one of these. Official and vendor pages are checked on the date shown; Deploi records are our own published decisions.
- Shopify Help Center, Importing and exporting customer lists
- Shopify Help Center, Metafield-based customer segment filters
- Shopify Help Center, Shopify-based customer segment filters
- Shopify Help Center, Shopify B2B features by plan
- Matrixify, Pricing
- Shopify Help Center, Creating customer segments
- Shopify Help Center, Migrate to Shopify
- Deploi Build vs. Buy, Build or Buy Customer Segmentation & RFM on Shopify?