AmeriCommerce → to Shopify

AmeriCommerce to Shopify: one migration, three brand names, many storefronts

AmeriCommerce is a hosted platform built for merchants who outgrew simple carts: several storefronts from one admin, wholesale pricing by customer type, variant-level inventory and a rule-based discount engine. It has also changed hands and names, so the same software is known as AmeriCommerce, Spark Pay and AmeriCommerce by Cart.com. This guide explains how we run an AmeriCommerce to Shopify migration: what the platform exports, how its multi-store and pricing setup maps to Shopify, how its ASP.NET URLs are redirected, and what it costs.

Why stores leave AmeriCommerce

• The owner’s focus has moved. Cart.com bought AmeriCommerce in January 2021 as the storefront layer of its ecommerce-as-a-service offer. Today Cart.com’s own site leads with fulfillment, marketplace services and growth marketing, and the storefront software is marketed mainly from americommerce.com.
• A small ecosystem. AmeriCommerce has its own integrations list, but finding an app, a theme developer or an agency for a specific need is usually easier on Shopify.
• Theme work needs specialists. Themes have full code access, which is powerful, but changes a Shopify merchant makes in the theme editor often need a developer who knows the platform.
• Checkout and payments. Shop Pay, accelerated wallets and Shopify’s checkout extensibility are strong reasons on their own for stores that sell to consumers.
• B2B is no longer the blocker. Customer type pricing was a reason to stay. Shopify B2B, with companies, catalogs, price lists and payment terms, now runs on every plan.

To be fair to AmeriCommerce, it is still maintained, its help center is still being updated, and few platforms match its multi-store depth. A merchant running many storefronts from one catalog should cost out the Shopify structure before deciding, which is what our audit does.

What migrates from AmeriCommerce to Shopify

AmeriCommerce exports CSV files from Tools > Data Export, with a store filter (or all stores) and saved column mappings. Its own backup guide names seven core exports: category, customer, order, product, product pricing, product variant and product variant inventory. Scheduled exports can also push files to an FTP or SFTP server. There is a REST API at /api/v1/ on the store domain, with OAuth 2 or a non-expiring admin token, which we use to fill the gaps the files leave.

Data	Source on AmeriCommerce	Moves to Shopify?
Products with item numbers, names, descriptions, base, retail and cost prices, weights, images, SEO fields	Product export, or the products resource in the API	Yes. The item number becomes the SKU, and the system ItemID is kept as the join key for redirects.
Variant groups, variants and surcharges	Product variant export	Yes, as options and variants, with each combination’s final price calculated from the surcharge rules.
Variant-level inventory	Product variant inventory export	Yes. On-hand quantities load per variant and location.
Personalizations and upload fields	Product editor, Options/Variants tab	Rebuilt as line item properties in the theme, so the customer’s text or file still reaches the order.
Categories and manufacturers	Category export; manufacturer pages	Yes, as collections and a vendor field, with the tree rebuilt in the menus.
Customers, addresses and customer custom fields	Customer export	Yes, with custom fields as customer metafields and marketing consent carried exactly.
Customer types, customer type pricing, store pricing, quantity pricing	Settings > People > Customer Types; product pricing export (Advanced Pricing Matrix)	Rebuilt as B2B companies, catalogs and price lists, discounts or Markets pricing. See below.
Orders with line items, variants, personalizations, tax, shipping, status and shipments	Order export (all stores) and the API	Yes. Real Shopify orders with original numbers and dates, the source store recorded, tracking where it exists, and refunds recorded as refunds.
Passwords	Not usable outside AmeriCommerce	No. Shopify cannot import another platform’s password hashes, so customers set a new password or use passwordless sign-in.
Product reviews	Native Product Reviews, or an app such as Yotpo	Yes, into Judge.me or your chosen app, matched on SKU. Native reviews are not one of the seven core exports, so we confirm the extraction route in the audit.
Gift certificates, discount methods, reward points	Marketing settings and the discount rule engine	Balances become Shopify gift cards; discounts are recreated by hand; points move to a loyalty app.
Themes, content pages, microstore settings	Theme export; content page export	Content pages move. Design is rebuilt as a Shopify theme.

AmeriCommerce URLs and the 301 redirect map

AmeriCommerce is an ASP.NET application (its pages still carry Web Forms view state), and its default URLs show it. Products use /store/p/7-Product-Name.aspx, categories /store/c/6-Category-Name.aspx, content pages /store/pg/5-Contact-Us.aspx, and manufacturer pages sit at the root, such as /Brand-Name.aspx. On the stores we tested, the /store/ form 301s to a shorter /p/7-Product-Name.aspx path while the canonical tag still names the /store/p/ form, so both versions can be indexed and linked. The number is what the platform resolves on: a link with an outdated slug is redirected to the current name.

On top of that, merchants can set a custom URL per product, category or page (for example /spa-enclosures.aspx or /folder/name.htm), change the Page URL Format per page type, and keep their own table under Settings > Search Engine > URL Redirecting. Microstores add paths such as /MicroStoreName.aspx, and each multi-store domain has its own set.

Shopify uses /products/handle and /collections/handle, so every form needs a 301. We build the map per domain from the sitemaps, the custom URL fields in the exports, the existing redirect table, a crawl and the Search Console page list, using the ItemID and category ID as the key. Both the /store/p/ and /p/ versions get entries, and each redirect is requested against the live domain before cutover.

Tools

Cart2Cart lists AmeriCommerce as a source, and LitExtension offers an AmeriCommerce to Shopify migration that connects through an API access token from a custom app in the AmeriCommerce admin. Cart2Cart is a partner of ours. Both are fine for a first pass on products and customers. Neither carries tracking numbers on shipped orders, refunded orders tend to arrive as plain paid orders, and redirects are built from guessed slugs rather than from the IDs and custom URLs AmeriCommerce actually serves. Neither tool rebuilds customer type pricing, multi-store structure or personalizations either, so we design those parts ourselves and use the API and exports to finish the orders and redirects.

How we run it

1. Audit. Export review, API token setup, store and microstore inventory, customer types and pricing matrix, variant and personalization analysis, integrations and fulfillment, URL inventory per domain. The output is a written, fixed-price scope.
2. Build in a free Shopify development store. As a Shopify Plus Partner we build in a development store, so you pay Shopify nothing until the store launches. Theme, checkout, payments, shipping and tax are set up here.
3. Catalog. Variant groups mapped to at most three options, surcharges resolved into variant prices, personalizations rebuilt, and store-specific catalogs mapped to Markets or separate stores.
4. Customers. Imported with consent and custom fields; customer types rebuilt as B2B companies, catalogs and price lists, or as tagged segments.
5. Orders. Full order history with original numbers, the source store, personalizations, refunds and tracking.
6. Redirects for every URL form on every domain, tested individually.
7. Sample, then full import, with reconciliation. A sample of each entity, including awkward cases, is signed off before the full run, and the full run is reconciled count by count and total by total against the exports.
8. Cutover with a delta sync. Orders and customers created in AmeriCommerce during the build come across at launch, then DNS moves.
9. Post-launch SEO evaluation. We watch 404s and redirects from launch day, and run the SEO evaluation once Google has re-crawled the store and the first real analytics exist.

Cost and timeline

Our migrations start from $2,500 for stores under 500 products and 5,000 orders ($3,500 for larger stores), which typically take six to eight weeks. B2B pricing, multiple storefronts and integrations are quoted as a fixed price after the audit, so you know the full cost before work begins. Terms are 50% to begin and 50% once the store is live and you are fully satisfied with the figures.

AmeriCommerce, Spark Pay or Cart.com: why the name matters

AmeriCommerce was founded in Texas in 2005. Capital One bought it in 2014 and sold it under the Spark Pay brand, with customer contracts assigned to Capital One Merchant Services. The AmeriCommerce team bought the company back in 2017, and Cart.com acquired it in January 2021. The help center now calls it both AmeriCommerce and Cart.com storefront software, and the admin login runs through Cart.com.

For a migration this matters in three ways. First, the data model and export screens are the same whichever name is on your invoice, so a Spark Pay era store exports exactly like a current one. Second, older stores often carry leftovers from each era: payment gateways configured under Spark Pay, integrations that are no longer supported, and URL formats changed along the way. We list them in the audit. Third, support now runs through Cart.com, and API help is a paid developer service there, so we plan any data we cannot get from the exports or API early rather than at cutover.

Multi-store: Shopify Markets or expansion stores

AmeriCommerce runs several complete storefronts, each with its own domain, theme and settings, on one shared database of products, customers and orders, plus lighter microstores on the main domain with their own catalogs and pricing. Shopify has no exact equivalent, so we choose per storefront:

• Shopify Markets when the storefronts differ mainly by country, currency or language. Each market can have its own domain or subfolder and its own pricing on a single store, which keeps one catalog and one order list.
• Separate Shopify stores (expansion stores on Shopify Plus) when the storefronts are different brands with their own theme, catalog and checkout. Inventory and catalog sync between them is then handled by an app or an integration, which we scope.
• B2B catalogs or customer segments for microstores, which usually exist to show one group of buyers its own products and prices.

Orders keep a record of the storefront they came from, so reporting by store still works after the move.

Customer types, price levels and quantity pricing to Shopify B2B

AmeriCommerce prices through an Advanced Pricing Matrix on each product: rows by customer type, store, quantity and date range, plus price calculators across stores. Customer types also control who sees prices, which products are hidden, which shipping methods apply and where buyers land after login. We map each piece:

• Wholesale price levels become Shopify B2B companies with catalogs and price lists. B2B runs on every plan, but plans below Plus are limited to three catalogs, so a store with many price levels often belongs on Plus. We settle that in the audit.
• Quantity pricing becomes B2B quantity rules and price breaks where the plan supports them, or automatic discounts with minimum quantities for retail buyers.
• Date-range sale prices become compare-at prices or scheduled discounts.
• Hidden products and login-gated pricing become catalog membership and B2B access; the variant matrix becomes a quick order list.

Membership comes straight from the customer export, so no trade buyer loses their pricing at launch.

Fulfillment and Cart.com services

Some AmeriCommerce merchants also use Cart.com for warehousing, marketplace selling or marketing. Moving the storefront does not have to end that relationship: Cart.com lists integrations with other commerce platforms, and we confirm with your account team how orders will reach the warehouse from Shopify before we schedule the cutover. Where fulfillment runs through another 3PL, ShipStation or a similar tool, we connect its Shopify app and test a live order end to end. Live UPS, FedEx or USPS rates at checkout need Shopify’s third-party carrier-calculated shipping, which comes with Advanced and Plus, or Grow on annual billing.

What you get at handover

Every AmeriCommerce migration ends with a reconciliation ledger from export counts to live Shopify counts for products, variants, customers and orders, per storefront, with order totals checked and every exclusion named; the pricing map showing where each customer type and price row went; the redirect verification list for every domain with the status each URL returned; an integration and fulfillment list with what replaced each one; and a recorded walkthrough of the Shopify admin for your team.

Questions we settle in the survey

• How many storefronts and microstores are live, and on which domains?
• Which customer types and price rows are still in use?
• Do products use personalizations, upload fields or variant surcharges?
• Is your fulfillment with Cart.com or another provider?
• Do you need live carrier rates at checkout?
• How much order history should come across?

Frequently asked questions

Start with the migration survey. For another hosted platform with a similar data model, see the BigCommerce to Shopify guide, and for a long-running hosted cart with a comparable history, the Volusion to Shopify migration page.