Migrate from Actindo Core1 to Acumatica

Actindo aggregates orders from multiple channels (Shopify, Amazon, marketplace) into a unified order format. We split each Actindo order into a corresponding Acumatica Sales Order, with channel name stored in a custom field (ExtChannelSource__c). The order total and lines map to Acumatica's SOOrder and SOLine tables.

Actindo allows one customer to have multiple channel-specific profiles with separate addresses and contacts. We merge these into a single Acumatica Customer record, creating one Customer Location per distinct shipping address found across Actindo channel profiles. The primary channel profile becomes the default Customer Location.

Actindo articles map directly to Acumatica Stock Items when the article has tracked inventory. Non-inventoried Actindo articles (e.g., digital goods, dropship-only SKUs) map to Non-Stock Items. We preserve the Actindo article ID in ExtArticleID__c on the Acumatica stock item for traceability.

Actindo warehouses, including their shelf/bin configuration, map directly to Acumatica Warehouses, preserving the original warehouse code, name, and address. While Actindo tracks a multi‑location flag that ties stock assignments to specific sales channels, this attribute has no equivalent in Acumatica and is therefore omitted during migration. Acumatica will allocate inventory to warehouses based on its own replenishment rules rather than channel logic.

Actindo maintains real-time stock levels per warehouse and article. Acumatica computes availability from posted transactions (IN Item Lot/Serial, IN Register entries). We create an opening inventory adjustment (IN Adjustment) to establish starting quantities matching Actindo's last-known stock snapshot, with a reference to the Actindo stock report date.

Actindo shipment records include carrier, tracking number, shipped lines, and timestamp. We map these to Acumatica Shipments linked to the corresponding Sales Order. Tracking data is stored in the Shipment's ShipmentNbr reference field. Actindo's delivery-time SLA flags transfer as custom fields on the Acumatica shipment.

If Actindo purchase orders are in scope, they map directly to Acumatica Purchase Orders. Vendor in Actindo becomes the Acumatica Vendor. PO lines map to POLine with the matching stock item. The PO status (open, closed, cancelled) carries over as the Acumatica status.

Any custom fields defined in Actindo DataHub require corresponding custom fields in Acumatica before migration. We document the Actindo DataHub field name, type, and pick-list values. Your Acumatica admin creates matching Usr-prefixed fields on the target DAC before we run the migration.

Actindo WorkFlow Engine definitions—including routing rules, ETL data transformations, and channel‑specific triggers—are tightly coupled to Actindo’s execution environment and have no direct counterpart in Acumatica. Consequently, these definitions cannot be imported and must be recreated using Acumatica Business Events, screen‑based automation schedules, or the native workflow engine. FlitStack extracts the existing workflow logic as a structured JSON file, providing your Acumatica team with a detailed reference for the rebuild effort and any necessary testing.

Actindo return records split into two Acumatica records: a Return Reason code (assigned to the original SO line via SO Adjustments) and an Inventory Issue (IN Issue) for items returned to the warehouse. The original Actindo return reason text is preserved in a custom field on the inventory issue.

Actindo’s channel connectors for Shopify, Shopware, Amazon, eBay, and similar marketplaces are third‑party integration modules, not data records, so they cannot migrate. To restore order ingestion, you must build new connectors—using Acumatica’s Import by Scenario for EDI, native integrations, or third‑party middleware such as SPS Commerce or Celigo. FlitStack records the active Actindo channels to guide your implementation planning.

Actindo invoices—especially those linked to completed shipments—are mapped to Acumatica AR Invoices, keeping the original invoice number, document date, total, and line items. Acumatica recalculates tax based on the tax zone assigned to the customer location; if the zones differ from Actindo’s tax setup, line‑level tax amounts may change. FlitStack provides a tax comparison report for each invoice so your team can align zones or apply overrides before final posting.