Order History & Fulfillments

Why Order History & Fulfillments needs Custom Migration

Past orders power customer support, returns, accounting, and lifetime value reporting. Each platform stores statuses, taxes, shipping lines, and fulfillments differently. When a standard migration cannot keep history usable in the new admin, Cart2Cart Custom Migration tunes order import for your operations.

Who this customization is for

• Support teams that look up historical purchases daily
• Finance and ops teams that need tax, discount, and fulfillment detail on old orders
• Stores migrating years of Magento, WooCommerce, or other order archives
• Merchants with heavy guest checkout volume that must stay linked by email

Common use cases

• Mapping source statuses to target workflow statuses
• Preserving guest checkout orders and linking them when emails match
• Importing fulfillment/shipment records, tracking numbers, or partial fulfillments
• Keeping tax lines, discounts, and refunds readable for audits
• Carrying order notes, tags, or internal comments support relies on

What Cart2Cart customizes

We define status maps, guest handling rules, and which order-related entities to include. Sample orders are reviewed with your team so tickets and reports still make sense after cutover.

Platform considerations

Order models differ sharply: Shopify fulfillments vs Magento shipments vs WooCommerce order notes and refund objects. Custom Migration maps what the target can store and documents gaps so ops is not surprised.

Note: The Target platform may require installing additional apps, plugins, or add-ons when a capability is not available by default. Custom Migration can map and import the data, but those Target-side apps/plugins often need to be installed and configured so the feature works in admin and on the storefront.

The best way to make sure everything is mapped correctly is to run a Demo Migration with your real Source platform data, then carefully check how entities look on the Target store before Full Migration.

Checklist for evaluating this customized migration

• Define how many years of orders you must keep and which statuses matter.
• Map source statuses to target workflow statuses (including canceled/refunded).
• Confirm guest order handling and email-based customer linking rules.
• List must-have fields: taxes, discounts, tracking, notes, tags.
• Review sample imported orders with support/finance before go-live.

How to apply for this customization

1. Browse Custom Migration or book a call.
2. Tell us source/target carts, order volume, and which years matter most.
3. List must-have fields: status, tracking, tax, notes, or customer links.
4. We scope effort, Demo where applicable, then schedule Full Migration with approved rules.

Self-service Additional Options vs Custom Migration

Order history migrates as a core entity; some related documents are Wizard Additional Options. Custom Migration is for status maps, guest linking, notes/tags, and fulfillment detail the Wizard cannot reshape.

• Migrate invoices, credit memos and shipments — Self-service: Move invoices/credit memos/shipments (and carriers where supported) via the Wizard. Choose Custom Migration when: Custom Migration when fulfillment models, partial shipments, or support-critical notes need tailored mapping.
• Preserve order IDs on Target Store — Self-service: Keep source order numbers/IDs when supported (typically requires clearing Target data first). Choose Custom Migration when: Custom Migration when native IDs cannot be forced and reference/metafield strategies are required—see also Preserve Order & Product IDs.

Availability depends on your Source → Target pair—confirm checkboxes in the Migration Wizard Entities / Additional Options step. See the Additional Options guide and Additional Options FAQ for pair-specific details. If Wizard options are not enough, schedule a Custom Migration call.

Already ran a self-service migration?

Yes—you can still apply this Custom Migration after a Wizard (self-service) run. Cart2Cart can restart migration with the customized rules; the Target store typically needs Clear current data on Target Store before Migration (or an equivalent cleanup of the entities from the previous self-service migration) so customized results are not mixed with the old import. Share your Source/Target carts and what already moved—Migration Experts will confirm the safest clear-and-rerun plan before Full Migration. Schedule a call if you already completed a Demo or Full Wizard migration and need customization next.

Case studies from real Custom Migrations

Cart2Cart Migration Experts have delivered custom work related to Order History & Fulfillments across 231 recorded customization projects spanning 67 Source→Target platform pairs. Below are pairs we see most often, the entities typically involved, and sample data volumes when available.

Platform pairs already in focus

• WooCommerce → Shopify — 39 customization projects
• Magento → Shopify — 32 customization projects
• PrestaShop → Shopify — 14 customization projects
• BigCommerce → Shopify — 13 customization projects
• Magento → WooCommerce — 12 customization projects
• Wix → Shopify — 12 customization projects

Entities commonly customized

• Orders — seen in 177 related projects
• Customers — seen in 148 related projects
• Products — seen in 127 related projects
• Categories — seen in 68 related projects
• Coupons — seen in 32 related projects

How much data was migrated

Among projects with recorded store size, median migration volume is about 14.5K records, with larger builds reaching roughly 125.5K at the 90th percentile and peaks near 2.6M. Exact counts depend on products, customers, orders, and related entities in scope.

Sample projects

• BigCommerce → Shopify — entities: Coupons 2.2M, Orders 302.3K, Customers 141.3K, Products 8.5K — total volume ~2.6M
• BigCommerce → WooCommerce — entities: Orders 524K, Customers 381.1K, Reviews 7.1K, Coupons 6.4K — total volume ~912.2K
• WooCommerce → Shopify — entities: Orders 529.8K, Customers 82K, Coupons 15.1K — total volume ~655.7K
• Magento → Shopify — entities: Orders 320.5K, Customers 8.2K — total volume ~328.8K

Every store is different—share your Source/Target carts and entity scope on a Migration Expert call and we will estimate a similar Custom Migration path.

What we need to scope order & fulfillment customization

Order statuses, tax lines, guest checkouts, and shipment objects differ by cart version, plugins, and how your ops team actually uses the admin. Two Magento→Shopify merchants can need completely different status maps.

Giving Migration Experts access to a staging clone (or production with a narrow read scope) lets us sample real orders, refunds, and fulfillments before we commit rules. When staging is unavailable, a database dump focused on order-related tables is an option—expect a deposit for dump restore and analysis, since that work happens before Full Migration pricing is locked.

Tip: Initial data-structure analysis is much more efficient when you prepare exact examples of the important attributes and fields on the Source, plus how each should be mapped on the Target store (sample products/customers/orders with field names, values, and desired Target destinations). Clear examples reduce discovery time and help Migration Experts quote and implement the customization accurately.

FAQs

Can every historical refund migrate perfectly?

Refund objects vary by cart. We preserve as much financial detail as the target allows and flag limitations early.

Will customers see old orders in their new accounts?

When accounts and emails link correctly, yes for supported flows. Guest history depends on linking rules we define with you.

How far back should we migrate?

Migrate what support and finance actually use—often 1–3 years—unless compliance requires more.

Need orders to remain support-ready after replatforming? Book a call with a Migration Expert.