Migrate from Actindo Core1 to Microsoft Dynamics 365 Business Central

Actindo Customer records map to Microsoft Dynamics 365 Customer entities. In Business Central, Customers are created as Customer records with address, contact, and payment terms preserved. In Finance and Operations, Customers are created as DirParty and LogisticsPostalAddress structures. We resolve the customer-specific address roles (invoice address, delivery address) using Actindo's address type flags and map them to the corresponding Dynamics 365 address purpose. Customer segment and pricing group fields in Actindo map to Dynamics 365 Customer Price Group or Customer Posting Group for ledger posting configuration.

Actindo Materials (SKU master with pricing, attributes, and variants) map to Microsoft Dynamics 365 Item records. In Business Central, Items are created with Item card data including No., Description, Unit Cost, Standard Cost, Unit Price, Item Category, Product Group, and Base Unit of Measure. We preserve the Actindo Material SKU as the Item No. for dedupe matching. Actindo variant codes map to Dynamics 365 Item Variants with Variant Dimensions for size, color, and style.

Actindo Articles extend Materials with channel-specific content, descriptions, images, and PIM data managed via the Omnichannel module. Articles are a separate export from Materials, and we preserve the relationship by tagging Article records with their parent Material SKU during extraction. In Dynamics 365, we reconstruct the relationship using Item Cross-References (one per channel: Shopify, Amazon, eBay, etc.) to store channel-specific SKUs and descriptions, and Item Tracking for any batch or serial numbers associated with the Article's fulfillment rules.

Actindo Orders (unified hub consolidating webshop, marketplace, POS, and B2B channels) map to Microsoft Microsoft Dynamics 365 Sales Orders. The Actindo order header fields (order number, order date, customer reference, shipping method) map to Sales Header fields. Each Actindo order line (product, quantity, unit price, discount) maps to Sales Line records with proper Item lookup resolution. The Actindo fulfillment status and tracking number fields migrate to Sales Header Shipping Notes and External Document Number. POS-sourced orders carry a store-location attribute that we map to the Dynamics 365 Location Code.

Actindo Warehouse entities define stock locations with bin-level structure for inventory tracking. In Business Central, these map to Warehouse entries and Bin content records. We migrate Warehouse definitions including bin structure, bin capacity, and zone assignment rules. In Finance and Operations Supply Chain Management, Warehouse entities map to Warehouses with the full WMS configuration including-directed picking-and-put-away rules, wave templates, and mobile device user assignments. Multi-warehouse routing configurations from Actindo are mapped to Dynamics 365 location directives.

Actindo Purchase Orders track procurement from vendors with PO headers, line items, and inbound receipts linked to Materials. We map PO headers and line items directly to Dynamics 365 Purchase Orders. Vendor-specific reference numbers and internal order numbers are preserved as external and internal document numbers. Receipt lines map to posted warehouse receipts or inventory movements depending on the destination organization's receiving workflow. We flag any Actindo PO with a status of partially received for manual reconciliation at cutover.

Actindo Invoice records link to Orders and track financial postings across accounting integrations. We extract invoice data including invoice number, invoice date, tax codes, payment terms, and payment status, then normalize to Dynamics 365 Posted Sales Invoices. In Business Central, invoice records land as Posted Sales Invoices (if posted) or Sales Invoice drafts (if not yet posted). Tax codes map to Tax Group and VAT Business Posting Group configurations that we establish during schema design. Payment status migrates to open or paid based on Actindo's payment status field.

Actindo Vendor master records store supplier data, payment terms, and lead times. We migrate Vendor records with contact information, purchasing defaults, and GL vendor posting groups to Dynamics 365 Vendors. Vendor-specific PO history is extracted as a linked reporting dataset rather than a live transactional import, since closed purchase orders in Actindo map to historical records that can be stored in a reporting archive or a custom table in Dynamics 365. Vendor lead times map to the Vendor's Default Inventory Lead Time field.

POS data from Venduo POS synced to Actindo includes transaction records and store cash register states. We extract POS transactions as Sales Orders with a store-location attribute mapped to the Dynamics 365 Location Code. Register reconciliations and cash drawer totals are stored as custom financial entries or journal lines rather than standard Dynamics 365 entities, since there is no native POS transaction entity in Business Central or Finance and Operations. The customer decides whether to post these as Cash Receipt Journals or store them in a custom register reconciliation table.

Actindo Workflow Engine definitions encode business process logic as low-code visual flows with routing rules, conditions, and actions. Workflows are not natively exportable in a standard schema. We capture screenshots and rule descriptions during extraction and deliver a written rule-mapping matrix that documents each Actindo workflow's trigger, conditions, routing actions, and recommended Dynamics 365 Power Automate or Business Central Workflow equivalent. The customer's admin rebuilds these in Power Automate or the Business Central workflow designer post-migration. We do not migrate workflows as executable code.

Actindo's DataHub module handles ETL transforms between source systems (webshop, marketplace, POS) and Actindo, supporting CSV, XML, and EDIFACT formats. We extract DataHub mapping configurations, transformation rules, and format specifications as a written document. These ETL mappings are not migrated as executable code because Dynamics 365 uses different integration mechanisms: Business Central uses APIs, web services, and OData; Finance and Operations uses Data Entity framework and Azure Data Factory for ETL. We document the DataHub mappings for the customer's integration team to re-implement using Azure Data Factory, Logic Apps, or Power Automate.

Actindo inventory stock levels export from the DataHub as warehouse-bin-level stock per Material SKU. We map these to Dynamics 365 Item Ledger Entries (opening inventory) and Warehouse Entries (bin-level postings). The inventory valuation method from Actindo (FIFO, Standard, Average) maps to the Dynamics 365 Costing Method on the Item card. We coordinate the inventory cutover to occur at a point when no orders are being placed in either system to avoid the dual-ERP inventory split problem. If the customer runs Actindo alongside a legacy ERP simultaneously, we flag which system is inventory-authoritative during the cutover window.