Migrate from Circle Commerce to Acumatica

Circle Commerce customers map directly to Acumatica ARCustomer (BAccount with Customer type). Circle's flexible custom properties on a customer record map to Acumatica `Usr` extension fields on the Customer entity — each must be declared with a field type before data loads. Primary contact email, phone, and company name carry over as direct field values.

Circle address records map to Acumatica's Address sub-record linked to ARCustomer via AddressID. Circle's address type flag (billing, shipping, pickup) is preserved as Address Attention or a custom pick-list field on the address record. Multiple addresses per customer in Circle collapse to multiple AddressID rows in Acumatica keyed by address type.

Circle inventory items map to Acumatica INItemStock for stocked goods or INItemNonStock for non-stocked. The item's SKU, description, unit cost, and unit of measure carry over directly. Circle's custom product attributes (any `Usr`-prefixed or named custom field on the item) require Acumatica custom fields on INItemStock; each one must be declared with the correct field type before the inventory import runs.

Circle's flat sales order structure splits into Acumatica's two-table model. Order-level fields (order number, date, customer reference, status, payment terms, shipping method) become fields on SOSalesOrder. Line items (SKU, quantity, unit price, warehouse, tax category) insert as child SOLine records with LineNbr assigned by Acumatica at insert time. The header record must exist before lines are inserted.

Each Circle order line becomes an SOLine record. The inventory item is resolved by SKU match to the INItemStock record migrated earlier. Quantity, unit price, and warehouse branch map directly. Discount amount and discount percent from Circle map to Acumatica's ManualDiscount and DiscountPercent fields on SOLine.

Circle purchase orders follow the same header-detail split as sales orders but target POOrder and POLine. Vendor resolution is by vendor name or vendor ID match against Acumatica's VPVendor records. Circle PO line items map to POLine by SKU; branch and warehouse default from Acumatica's receiving warehouse configuration if not specified in Circle.

Circle fulfillment records map to Acumatica SOShipment. Carrier code, tracking number, shipment date, and shipped quantity carry over directly. The shipment is linked to the originating SOSalesOrder by OrderNbr. If Circle tracks partial shipments, each partial shipment becomes a separate SOShipment with its own line quantities summing to the original order.

Circle's payment term labels (Net 30, 2/10 Net 30, etc.) map to Acumatica Terms records by value-by-value lookup. If Circle stores custom payment term names not in Acumatica's default Terms table, those are flagged for creation in Acumatica before the full migration runs. The migration plan surfaces any unmapped term values as a pre-flight action item.

Circle's most powerful (and migration-critical) feature is its ability to attach arbitrarily named custom properties to any entity. Each discovered custom property is evaluated: if a typed Acumatica custom field with a matching semantic purpose exists, it is used directly; if no match is found, an Acumatica `Usr`-prefixed custom field is created with the appropriate field type before data loads. Empty or null custom property values are skipped to avoid Acumatica field-type errors.

Circle workflow automations, sequence triggers, and email notification rules have no Acumatica equivalent in the data migration scope. We export Circle workflow definitions as JSON for each discovered automation and deliver an Acumatica Business Events + Automated Actions rebuild plan. Your Acumatica admin uses the exported definitions as a functional specification to recreate trigger-action logic in Acumatica.

Circle saved searches and custom reports are query-based platform objects that do not export as transferable definitions. We document each saved search's filter columns, sort order, and output fields as a plain-language rebuild specification. These specifications are used to create Acumatica Generic Inquiries (GI) for list-type queries and Report Designer layouts for printable reports.