Coupons & Discounts

Why Coupons & Discounts needs Custom Migration

Coupon engines differ by cart: conditions, usage limits, stacking, and discount types rarely map 1:1. Custom Migration for coupons & discounts ports or rebuilds promotional rules so active campaigns can continue—and historical order discount lines stay accurate in reports.

Who this customization is for

• Merchants mid-campaign who cannot drop active codes at cutover
• Teams with Magento cart rules or Woo coupons moving to Shopify discounts
• Finance owners who need discount lines on historical orders
• Stores with segment- or group-based promotions

Common use cases

• Moving Magento shopping cart rules or WooCommerce coupons to Shopify discount codes
• Preserving usage limits, expiry dates, and minimum order conditions
• Rebuilding BOGO or free-shipping rules that have no direct equivalent
• Keeping discount lines on historical orders for reporting
• Segment- or customer-group-based coupons that need tag/role mapping first

What Cart2Cart customizes

We inventory active and historical promotions, map what the target supports natively, and rebuild edge cases where needed. Sample codes are tested before you announce campaigns on the new store.

Platform considerations

Shopify Discount APIs/codes, WooCommerce coupons, and Magento sales rules differ in stacking and conditions. Custom Migration translates intent, not just code strings.

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

• Separate active campaigns from historical-only discount data.
• List coupon types (percent, fixed, free shipping, BOGO) and stacking rules.
• Map usage limits, expiry, and minimum-order conditions to the target.
• Note customer-group or segment coupons that need tags/roles first.
• Test sample codes on the target before announcing post-launch promotions.

How to apply for this customization

1. Browse Custom Migration or schedule a consultation.
2. Share platforms and whether you need active codes, history only, or both.
3. Export or list key coupon types (percent, fixed, free shipping, BOGO).
4. We scope rebuild vs map, Demo-verify samples, then migrate with your launch plan.

Self-service Additional Options vs Custom Migration

There is no dedicated self-service Additional Option that fully ports coupon engines between carts. Coupons may migrate as an entity for some pairs with limited rule fidelity—Custom Migration rebuilds conditions the Wizard cannot map 1:1.

• Coupons / discount codes (entity migration where supported) — Self-service: Migrate coupon records when your cart pair lists Coupons as a migratable entity—expect condition gaps. Choose Custom Migration when: Custom Migration for Magento cart rules, BOGO, stacking, segment-based promos, and Target discount rebuilds.

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 Coupons & Discounts across 43 recorded customization projects spanning 19 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 — 11 customization projects
• Magento → Shopify — 8 customization projects
• Wix → Shopify — 4 customization projects
• PrestaShop → Shopify — 4 customization projects
• BigCommerce → Shopify — 2 customization projects
• BigCommerce → WooCommerce — 1 customization project

Entities commonly customized

• Coupons — seen in 36 related projects
• Orders — seen in 34 related projects
• Customers — seen in 32 related projects
• Products — seen in 29 related projects
• Categories — seen in 18 related projects

How much data was migrated

Among projects with recorded store size, median migration volume is about 28.3K records, with larger builds reaching roughly 655.7K 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 250.2K, Coupons 125.6K, Customers 46.1K, Products 3.4K — total volume ~250.2K

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 coupon & discount customization

Promo rules, usage limits, cart conditions, and gift cards are among the least portable entities between carts. Your coupon catalog and how it interacts with taxes/shipping is unique.

Prefer staging or production access so Experts can sample active, expired, and edge-case codes. Without access, provide a database dump of coupon/rule tables for offline review—dump inspection usually requires a deposit to cover restore and rule decoding before Custom Migration scoping.

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

Will every Magento cart rule become a Shopify discount?

Simple rules often map; complex conditions may be rebuilt or replaced with apps.

Can used coupons keep usage counts?

When the target stores usage data we can map; otherwise we document limits.

Should we pause campaigns during cutover?

Usually yes for a short window until codes are verified on the new store.

Don’t lose mid-campaign codes at cutover—talk to Cart2Cart.