Migrate from ProcessWare ERP to Microsoft Dynamics 365 Business Central

Formulation Recipes are ProcessWare's core F&F object storing compound hierarchies, ingredient ratios, version history, and regulatory classification. Dynamics 365 has no native formulation object. We map the recipe header to a D365 Item record with custom fields capturing version number, regulatory classification, and IFRA status. The recipe's ingredient list maps to BOM lines on the Item. Compound sub-assemblies that are themselves formulations map to D365 BOM lines referencing those Items, creating a multi-level BOM tree that preserves the original hierarchy but flattens it under a single parent Item.

ProcessWare Production Orders carry planned quantities, scheduling constraints, facility routing, and a link to the originating formulation. In D365 F&O, these map directly to Production Orders with routing and job scheduling. In Business Central, Production Orders are available in the Manufacturing extension; if Business Central is the destination, we configure the Manufacturing extension first and map Production Order status, location code, and scheduled dates from ProcessWare. If D365 F&O is the destination, routing operations carry over via production route configuration.

ProcessWare multi-level BOMs support sub-assemblies that are themselves other formulations, creating recursive ingredient relationships. D365 BOMs support multi-level structures but require that each BOM Version be tied to a specific Item. We create a D365 BOM and BOM Version for each ProcessWare formulation revision, resolving recursive references by breaking the cycle at the designated root formulation and using BOM line Items for all sub-assembly ingredients. Allergen declarations and ingredient percentages stored on BOM lines migrate as custom fields on the BOM line.

Quality Records in ProcessWare link test results and QC documentation to specific production batches and raw material lots with passing criteria and inspector assignments. In D365 F&O, Quality Associations define sampling and test requirements per item or order type, and Quality Journals record test results. We map ProcessWare quality test types to D365 quality test types, batch identifiers to D365 lot numbers, and inspector assignments to D365 workers. In Business Central, quality data maps to item tracking fields and custom quality result fields on the Item card.

ProcessWare Customer records include full contact details, account hierarchies, and sales history from the integrated CRM component. These map directly to D365 Customer records. The CRM component's inquiry-to-account lifecycle means ProcessWare stores both prospect inquiries and active customer records in the same table; we split these into D365 Contact (for individuals with no account relationship) and Customer (for organizations) before migration, preserving any inquiry-stage notes as custom fields on the Contact.

Vendor profiles in ProcessWare include certification status, material qualifications, and performance history for regulatory compliance tracking. These map to D365 Vendor records with vendor-specific compliance fields carried as custom fields. If ProcessWare stores material qualification dates and certificate expiry tracking, we map these to D365 Vendor rating or compliance custom fields. Vendor-ledger history and purchase order history migrate to D365 vendor ledger entries.

ProcessWare supply chain transactions cover purchase orders, receipts, and outbound shipments for raw materials and finished goods with full traceability to production batches. These map to D365 Purchase Orders and Sales Orders with line items linked to the corresponding Items and batch or lot numbers. D365's warehouse management module tracks the same lot-level traceability as ProcessWare, so batch number, expiration date, and raw material lot linkage carry over as item tracking entries on each transaction line.

IFRA compliance data, SDS documents, allergen declarations, and certificate of analysis files are stored in ProcessWare with links to specific formulations and raw material lots. D365 does not have a native compliance document repository. We map compliance documents to D365 attachments on the relevant Item or Vendor records, and we create a custom Compliance Record entity in D365 to store IFRA classification codes, restriction categories, and allergen flag fields. The document files themselves migrate as blobs to D365's attached SharePoint or OneDrive for Business document management.

The Keka HRMS integration documentation for ProcessWare confirms that custom fields are accessible via read/write operations on the source platform. We map ProcessWare custom fields to equivalent D365 custom fields on the corresponding entities (Item, Vendor, Customer, Production Order). Because ProcessWare's full schema is undocumented, we cannot infer all custom field semantics; we document every unmapped or ambiguous custom field in a custom field inventory report for the customer's functional team to resolve before migration completes.

Supporting documents attached to formulations, quality records, and transactions in ProcessWare (COAs, spec sheets, compliance certificates) migrate to D365's integrated SharePoint or OneDrive for Business document management, attached to the corresponding record (Item, Vendor, Production Order, Quality Journal). File types and folder structures vary by ProcessWare configuration; we extract all attachments during the data acquisition phase and reattach in D365's document management framework with a folder hierarchy matching the source organization.

ProcessWare inventory tracks raw material lots, intermediate compounds, and finished goods with real-time traceability from raw material lot to finished batch. We map these to D365 Items with Item Tracking Groups enabled for both lot and batch tracking. Each inventory transaction (receipts, issues, adjustments) migrates as a D365 Item Ledger Entry, preserving the lot number linkage between raw material receipt and finished goods receipt for traceability reporting in Power BI.

ProcessWare allergen tracking is native to the F&F data model, storing declared allergens per formulation with source ingredient linkage. D365 has no native allergen field on Item. We create custom multi-select or boolean fields on the D365 Item record for each allergen category relevant to the customer's product range (e.g., Contains Gluten, Contains Soy, Contains Milk, Contains Nuts, Contains Crustaceans). The allergen declaration document migrates as a compliance attachment on the Item record.