Taxes & Pricing Rules

Why Taxes & Pricing Rules needs Custom Migration

Tax classes, VAT setups, and tax-inclusive vs exclusive catalogs rarely transfer automatically. Misaligned rules create wrong storefront prices and broken historical totals. Custom Migration for taxes & pricing interprets product prices and order tax lines so compliance and merchandising expectations stay consistent.

Who this customization is for

• EU/UK merchants with VAT-inclusive catalogs
• Stores with complex tax classes or multi-country tax rules
• Finance teams that need readable tax on historical orders
• Catalogs using special/compare-at prices that map differently by cart

Common use cases

• EU VAT and tax-included catalogs moving to platforms with different tax engines
• Remapping Magento/Woo tax classes to Shopify or target tax settings
• Preserving readable tax lines on historical orders for accounting
• Adjusting special price / compare-at fields when pricing models differ
• Multi-country tax class assignments that need explicit rules

What Cart2Cart customizes

We clarify whether source prices are tax-inclusive, map tax classes, and validate sample products and orders. Finance stakeholders can review totals before cutover.

Platform considerations

Shopify Markets/tax settings, WooCommerce tax classes, and Magento tax rules behave differently at catalog vs checkout. Custom Migration aligns migration math with how you will configure the live target.

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

• Confirm tax-inclusive vs exclusive catalog pricing on source and target.
• List tax classes/zones used today and how they should map.
• Align special/compare-at price fields with the target pricing model.
• Decide whether historical order tax lines must remain reportable.
• Have finance review sample product and order totals after Demo.

How to apply for this customization

1. Schedule a Call and mention taxes / pricing rules.
2. State platforms, primary selling countries, and tax-included vs excluded pricing.
3. Share how tax is configured today (classes, zones, apps).
4. We scope custom rules, Demo-verify samples, then proceed to Full Migration.

Self-service Additional Options vs Custom Migration

Product prices migrate with products. Tax configuration can be a Wizard Additional Option. Custom Migration aligns tax-inclusive catalogs, class maps, and historical order tax readability.

• Migrate the store tax configuration — Self-service: Transfer tax display/calculation settings where the Wizard supports this option. Choose Custom Migration when: Custom Migration for VAT-inclusive price interpretation, tax class remaps, and finance review of sample totals.

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 Taxes & Pricing Rules across 139 recorded customization projects spanning 51 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 — 20 customization projects
• Magento → Shopify — 15 customization projects
• PrestaShop → Shopify — 15 customization projects
• Magento → WooCommerce — 9 customization projects
• PrestaShop → WooCommerce — 9 customization projects
• Magento → Magento — 4 customization projects

Entities commonly customized

• Products — seen in 70 related projects
• Orders — seen in 50 related projects
• Customers — seen in 45 related projects
• Categories — seen in 28 related projects
• Coupons — seen in 8 related projects

How much data was migrated

Among projects with recorded store size, median migration volume is about 9.4K records, with larger builds reaching roughly 120K 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
• Magento → Shopify — ~371.3K records migrated
• WooCommerce → Shopify — entities: Orders 110.8K, Products 18.2K, Customers 14.6K, Categories 147 — total volume ~144.4K
• Shift4Shop → Shopify — ~88.2K records migrated

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 tax & pricing customization

Tax classes, inclusive/exclusive pricing, catalog rules, and compare-at logic are tightly coupled to how your Source was configured over years of promotions and regional settings. Individual store setup matters more here than platform defaults.

Granting staging or production access lets us verify tax display, rule stacks, and edge-case products before coding. If you cannot open the store, a database backup dump with tax/price tables can be reviewed offline—dump work generally requires a deposit for restore and financial-field validation.

FAQs

Will checkout tax equal source checkout tax automatically?

Not always—target tax engines differ. We align catalog migration and call out live tax configuration work.

Can historical orders keep tax breakdowns?

As far as the target order model allows. We prioritize finance-readable detail.

Do price lists and B2B pricing migrate?

Advanced price lists often need Custom Migration or plugin/addon data work—tell us early.

Avoid post-launch price surprises—talk to Cart2Cart.