Migrate from eCommerce Pro to Acumatica

eCommerce Pro products map to Acumatica StockItems. Each product variant in eCommerce Pro becomes a separate StockItem row with the base SKU stored as InventoryCD. Inventory N:1 against a single StockItem is resolved by splitting each variant into its own StockItem in Acumatica so warehouse availability tracks per SKU rather than per parent product.

eCommerce Pro variants (colour/size matrices) split into individual StockItem rows in Acumatica. The variant's combined attribute string is decomposed into separate values stored in the Item Class definition and custom fields (UsrColor, UsrSize) on the StockItem DAC. This avoids the Acumatica constraint where one StockItem cannot have conflicting availability by dimension.

eCommerce Pro product images are downloaded and re-uploaded to Acumatica's file storage. We populate ImageUrl on the StockItem using the uploaded file URL. Image ordering (which image is primary) is preserved in a sort-order custom field (UsrImageSortOrder__c) since Acumatica has no native primary-image flag on StockItem.

eCommerce Pro stock quantities per variant map to Acumatica Item Warehouse records per branch. If eCommerce Pro uses a single inventory pool and Acumatica has multiple branches, we apply the quantity to the primary branch and zero to others — your team specifies which branch is default or splits across locations before migration runs.

eCommerce Pro customer records map to Acumatica Customers with a primary Contact and Address attached. Acumatica requires a Class ID on every Customer; we assign a default class (CUSTOMER) and flag records where a different class is recommended based on the customer's order volume or tax status for your admin to review post-migration.

eCommerce Pro customer tags and segments have no native Acumatica equivalent — Customer does not have a native tagging or segmentation object. We preserve tags as a delimited note on the Customer record or create a custom string field (UsrCustomerTags__c) for reporting and segmentation within Acumatica.

eCommerce Pro orders map to Acumatica SalesOrders. For paid orders, the corresponding ARInvoice is generated. eCommerce Pro order status (pending, processing, completed, cancelled) maps to Acumatica SalesOrder status (On Hold, Pending, Open, Completed, Cancelled) based on the payment state and fulfillment state combination.

Each order line in eCommerce Pro becomes a SalesOrderDetail line in Acumatica, linked to the target StockItem via InventoryCD. Line-level discounts from eCommerce Pro map to the Discount Amount field on the detail line; percentage discounts require an Acumatica Discount Code setup post-migration.

eCommerce Pro shipping method names (e.g., 'Standard Shipping', 'FedEx Ground') are mapped value-by-value to Acumatica Carrier records. If no matching Carrier exists in Acumatica, we flag it for your admin to create before orders migrate. Shipping cost from the order is stored as a freight custom field on the SalesOrder (UsrFreightCost__c) for reconciliation.

eCommerce Pro discount codes and coupons have no direct Acumatica equivalent at the order level. Percentage and fixed-amount discounts applied at checkout are stored as line-level discount notes in the migration, and we provide a Discount Code setup guide for your Acumatica admin to configure the promotional rules post-migration so future orders apply discounts automatically.

eCommerce Pro product collections map to Acumatica Item Class hierarchy. We create Item Classes matching your top-level collection names and store the full collection path in a custom text field (UsrSourceCollections__c) on each StockItem so reports can filter by the original storefront taxonomy.

eCommerce Pro CMS pages, blog posts, and URL slugs have no Acumatica equivalent — Acumatica is an ERP, not a CMS. We export page titles and URL slugs as a reference CSV so your web team can recreate the content and implement 301 redirects from the old storefront URLs to the new site.