Migrate from AltheaSuite to Microsoft Dynamics 365 Business Central

AltheaSuite Items map to Dynamics 365 Business Central Product2 records. Standard fields (Item No., Name, Base Unit of Measure, Item Category, Product Group, Purchasing and Sales inventory posting groups) migrate directly. Reorder levels and reorder quantities map to Reorder Point and Reorder Quantity on the Product. AltheaSuite custom Item fields (user-defined properties not discoverable via API) are enumerated during discovery by requesting field definitions from the customer and are mapped as custom properties on Product2 in the destination.

AltheaSuite custom Item fields (dropdown, text, numeric, date types) have no public discovery mechanism, so we request the full list of field definitions from the customer during schema profiling and verify them against the live system during the profile walkthrough. Each field type is converted explicitly to its nearest Dynamics 365 field type (Option Set for dropdown, Text for text, Decimal for numeric, Date for date). Field names are preserved in the custom property label with a migration-source prefix for audit.

AltheaSuite stores serial-to-item assignments as separate child records with no direct Business Central equivalent. We extract the full serial-to-item mapping as a child table during export, then create corresponding Item Tracking Lines (tracking code with serial number assignment) in Dynamics 365 linked to the relevant Item Ledger Entry at time of receipt. We flag any orphaned serial records that reference a non-existent Item and present them for manual resolution before finalizing the import.

AltheaSuite lot-controlled Items carry lot number and expiry date metadata. We migrate Lot Number to the Item Tracking Line lot number field and expiry date to the Item Tracking Line expiration date field in Business Central. FEFO (First-Expired-First-Out) logic in Business Central uses the expiry date to drive warehouse picking priority, so we ensure expiry dates are migrated as actual Date fields rather than embedded text. Any lot record without a parent Item goes to the reconciliation queue.

AltheaSuite Customer records map directly to Business Central Customer records. Address data (street, city, state/province, postal code, country) maps to the Address fields on the Customer Card. Contact name, phone, email, and any customer-specific pricing or payment terms transfer to the respective fields on the Customer. Customer number in AltheaSuite becomes the No. field in Business Central, with the original AltheaSuite ID preserved in a migration reference field.

AltheaSuite Vendor records map to Business Central Vendor records with contact details, addresses, and supplier-level fields intact. The vendor-managed inventory flag (a boolean property on the Vendor record in AltheaSuite) migrates as a custom field on the Vendor Card. Vendor number becomes the No. field in Business Central with the original AltheaSuite ID preserved in a migration reference field for cross-system audit.

AltheaSuite Purchase Orders (header and line items) map to Business Central Purchase Orders. PO number becomes the External Document No. field, line items map with Item No., quantity, and direct unit cost, and the order status maps to the Status field. Multi-currency amounts and landed-cost fields require explicit value mapping against the destination currency settings and are flagged as configuration items during scoping. Received and invoiced quantities are not carried forward; open POs are imported as pending orders.

AltheaSuite Sales Orders map to Business Central Sales Orders with header data (order number, customer reference, shipping address), line items (Item No., quantity, unit price, line discount), and delivery assignment preserved. Fulfillment status (open, partially shipped, shipped, cancelled) maps to Business Central Status. Orders with a delivery module in AltheaSuite retain their delivery linkage as a shipping address reference. Invoiced orders in AltheaSuite are not recreated as Sales Orders but are referenced in the reconciliation report as historical closed records.

AltheaSuite Work Orders map to Business Central Production Orders. The Work Order header (order number, status, scheduled start and end dates, assigned work center) migrates to the Production Order header. The multi-level BOM from AltheaSuite is flattened during the transform phase: each nested sub-assembly becomes a Production BOM line item at the correct version, and the parent item of the Work Order becomes the Production Order item. Step-level labor and machine time entries migrate as routing lines if the destination has the Routing feature enabled.

AltheaSuite multi-level BOMs with nested sub-assemblies require flattening before import into Business Central. We extract the full BOM hierarchy, identify the top-level manufactured item, list all components with their quantities and unit of measure, and reconstruct the parent-child relationships as a single-level Production BOM with version. Routing steps (work centers and machine centers) are mapped if the destination includes the Manufacturing module. Any BOM component that references a non-migrated Item is flagged and held for manual resolution.

AltheaSuite Customer records may have multiple associated contact records (names, roles, phone, email, address). Each contact migrates as a Business Central Contact linked to the parent Customer. Contact type (order contact, invoice contact, primary buyer) maps to the Type field on the Contact Card. Primary contact is flagged with the Primary Contact checkbox. If a contact in AltheaSuite has no associated Customer, the contact is held in the reconciliation queue.

AltheaSuite Vendor contacts migrate to Business Central Contacts with the Vendor set as the Business Relation on the Contact Card. Contact name, role, phone, and email map to the corresponding fields. If the same person appears as a contact on both a Customer and a Vendor (e.g., a broker or distributor contact), the Contact record is created once with both Business Relations linked via Contact Business Relations entries.