Migrate from Guardian Software to Microsoft Dynamics 365 Business Central

Guardian Customer records with address, contact details, and classification map to Business Central Customer or Finance & Operations CustTable. Customer number from Guardian becomes the account code; payment terms and customer posting groups are mapped via a configuration table before import. Multi-address customers (invoice vs delivery) require the Dynamics 365 address-role model to be active on the destination, as Finance & Ops allows multiple address purposes per customer.

Guardian Production Orders map to Dynamics 365 Production Orders with order status, quantity, scheduled dates, and work-center routing transferred as typed records. The Guardian production-order number becomes the ProdId; routing steps from Guardian's Work Center Routing map to Operations in Dynamics 365 Finance & Ops or to the Production BOM and Routing in Business Central. Where Guardian stores furnace-specific heat numbers and batch IDs, these transfer to the Production Order's lot or serial number field.

Guardian raw material, alloy, and finished casting inventory records map to Dynamics 365 Item or InventTable with unit-of-measure conversions preserved via the item's unit-of-measure group. Current inventory balances (quantity and value) migrate as inventory on-hand journal entries posted to the appropriate location and warehouse codes. Bin-level location data from Guardian maps to the Dynamics 365 warehouse location hierarchy if the destination uses multi-bin inventory.

Guardian Quality Records with inspection results, non-conformance codes, and certificates of conformance map to Dynamics 365 Quality Management entities. Inspection characteristics from Guardian transfer as Quality Association test variables; disposition status (accept, reject, rework) maps to the corresponding Dynamics 365 disposition codes. Attachments (PDFs, CoCs) migrate as document attachments linked to the quality record via SharePoint or the native attachments model.

Guardian Equipment records with maintenance schedules, depreciation data, and location assignments map to Dynamics 365 Fixed Assets. Acquisition cost, depreciation method, useful life, and location from Guardian transfer to the Fixed Asset card fields. Maintenance schedules migrate as Asset Service Tasks with recurrence patterns preserved. Any Guardian asset linked to a production order carries the asset reference forward into the Operations resource assignment.

Guardian Work Center Routing with step sequences, labor hours, machine hours, and setup times maps to the Operations Resource Group and Resource model in Finance & Ops, or Work/Machine Centers in Business Central. Step count, cycle time, and route operations transfer as typed routing records. Foundry-specific resource groups (furnace, pour, shakeout, heat treat) map to Resource Groups with capacity calendars configured per work-center availability.

Guardian account codes and cost-center structures for financial integration require a configuration mapping table before migration. Foundry-specific cost pools (scrap cost, rework cost, tool wear) must map to G/L accounts in Dynamics 365 to maintain GL continuity in the destination. We extract the full Guardian cost-center hierarchy, map each code to a Dynamics 365 account, and validate total period balances post-import. Account validation against the Guardian trial balance is a required gate before production migration.

Guardian user accounts with role-based access control map to Azure Active Directory (Entra ID) users in the Dynamics 365 tenant. Role names and permission sets vary between Guardian and Dynamics 365, so we produce a role-mapping matrix during discovery and recommend a post-migration access review with the customer's security admin. We do not provision the Entra ID users themselves; we provide the role matrix and the customer provisions the identities.

Guardian user-defined fields on standard objects (alloys, heat codes, foundry lot numbers, scrap codes) are extracted with their data types, picklist values, and parent object. We create equivalent custom fields in Dynamics 365 using the extension model (AL extensions in Business Central; DevTools extensions in Finance & Ops) and map the values during migration. Complex formula fields from Guardian require re-implementation as computed columns or Power BI measures, which is documented separately.

Historical journal entries for cost accounting and period closes transfer as general journal batches with header and line structure preserved. Entry date, account, debit, credit, and description migrate directly. Reversing entries and adjustment flags are preserved where supported by the destination posting model. Deep historical data (more than 5 fiscal years) is typically scoped as an archive read-only migration or left in the Guardian database for reference, per the customer's data retention policy.

Open and closed PO headers with line items, quantities, prices, and vendor assignments migrate to Dynamics 365 Purchase Orders. Guardian vendor cross-references are remapped to the destination vendor account codes resolved during the vendor mapping phase. Receipt and invoice matching status from Guardian transfers to the corresponding Dynamics 365 posting status fields. Closed POs migrate with their final receipt quantities for historical reporting continuity.

Engineering drawings, batch sheets, compliance certificates, and operator logs stored as file attachments in Guardian migrate alongside their parent records and re-associate in Dynamics 365 via the document handling model. Filename and file type are preserved; file size and content are verified against a hash during import. We recommend SharePoint document management for the destination to align with Microsoft 365 integration, and we configure the SharePoint document location on the relevant entity.

Guardian BOM structures for casting recipes, alloy ratios, and material compositions transfer to Dynamics 365 BOM versions with line items mapped to the migrated Item records. BOM quantities, scrap percentages, and routing consumption factors are preserved. Where Guardian stores version-controlled BOMs, the Dynamics BOM version number and status fields are populated to maintain engineering revision history.