Migrate from Access SupplyChain to Microsoft Dynamics 365 Business Central

Access SupplyChain Customer records map to a combination of Dynamics 365 Account (the organisation) and Contact (the person). The customer name and address become Account.Name and Account.PrimaryAddress; primary contact details become a Contact record linked via the Account. We resolve the 1:N relationship by identifying the primary contact per customer and creating Contact records for additional named contacts found in the Access SupplyChain contact table. Payment terms from Access SupplyChain map to Dynamics 365 PaymentTerm lookups.

Access SupplyChain Supplier records map directly to Dynamics 365 Vendor records. Supplier name, address, and bank details transfer to Vendor.name, Vendor.address, and the VendorBankAccount entity. Category assignments in Access SupplyChain map to Vendor groups in Dynamics 365. Any supplier-to-customer relationship records require explicit mapping to the Account-Vendor cross-reference table.

Open purchase orders migrate to Dynamics 365 PurchaseOrderHeader and PurchaseOrderLine records. Access SupplyChain status values (Draft, Sent, Received, Closed) map to the corresponding PurchaseOrderStatus values. Historical closed orders migrate as read-only records unless the destination org requires full history. PO line items resolve item SKUs to the Released Products table during import. We flag any Access SupplyChain POs with outstanding goods-receipt lines that span multiple periods.

Access SupplyChain Item master records map to Dynamics 365 ReleasedProduct. The item SKU (hs_sku equivalent in Access SupplyChain) becomes ProductNumber; description, unit of measure, cost price, and sales price map to Name, DefaultUnitOfMeasure, CostPrice, and Price fields respectively. Where items have been merged or archived in Access SupplyChain, we flag duplicates during discovery and apply a deduplication strategy before import. ItemBomType and RouteId are created as configuration records if manufacturing data is present.

Access SupplyChain Warehouse records map to Dynamics 365 Site and Warehouse entities. The Site defines the location; the Warehouse is linked to the Site and holds bin locations (storage dimensions). Stock-on-hand figures are extracted as a snapshot and applied at go-live to avoid mid-migration discrepancies caused by in-flight goods receipts or issues during the extraction window.

The chart of accounts migrates to Dynamics 365 MainAccount with AccountType and FinancialDimension configuration. Multi-company Access SupplyChain deployments with distinct account structures per legal entity require explicit mapping per entity. We interview the customer's finance team to build the account mapping matrix before any transactional data is loaded. Dimensions in Dynamics 365 (Cost Centre, Department, Project) map from Access SupplyChain segment codes if present.

Outstanding Access SupplyChain vendor invoices migrate as open VendorInvoice records in Dynamics 365. Payments in transit and unresolved allocations are flagged in the reconciliation worksheet to prevent double-posting. Partial receipts and credit notes are mapped to VendorInvoiceLine with negative quantity or credit note adjustment types. The vendor lookup resolves using the VendorId established during the Supplier migration.

Outstanding Access SupplyChain customer invoices migrate as open Dynamics 365 CustomerInvoice or FreeTextInvoice records. Credit notes, credit memos, and partial receipts are mapped to corresponding reversal types. Payment allocations that span the extraction window require manual review and re-application using the reconciliation worksheet we deliver at cutover.

Documents attached to supplier records, item records, and purchase orders in Access SupplyChain are exported from the document management layer and linked to their corresponding destination records in Dynamics 365 via SharePoint Online document locations or the Note entity. Very large files or non-standard formats are flagged during scoping for size compliance.

Custom fields created via Access Studio are enumerated during discovery and mapped individually to equivalent Dynamics 365 fields. Fields with unsupported data types such as embedded objects or binary blobs are flagged and handled per a customer-approved exception plan. The destination schema is pre-created with custom fields before any transactional data import begins.

Access SupplyChain user accounts map to Dynamics 365 User records with role assignments. Role naming conventions differ between Access SupplyChain versions and Dynamics 365, so role mapping is performed manually during scoping. We map each Access SupplyChain role to the nearest Dynamics 365 Security Role and document any permission gaps for the customer's admin to address post-migration.

If Access Coins Evo is active, project-level cost tracking, supplier risk scores, and AI-assisted forecasting data are scoped separately. Project headers map to Projects in Dynamics 365 Project Operations or to Cost Categories depending on the destination module. AI-assisted forecast scores do not migrate as predictive models; we deliver a written description of the forecasting logic for the customer's analytics team to re-implement using Power BI or Azure Machine Learning.