Migrate from Prowess ERP to Microsoft Dynamics 365 Business Central

Prowess ERP Chart of Accounts records map directly to Microsoft Dynamics 365 G/L Account (MainAccount) with account code and description preserved. Where Prowess ERP uses implementation-specific Cost Centre prefixes embedded in account codes, we split them into separate Financial Dimension values in Dynamics 365 and map the parent Cost Centre to a Dimension set. This re-modelling requires one to two days of validation against the trial balance before the import phase runs.

Prowess ERP Cost Centre hierarchies are implementation-specific with no canonical schema reference. We extract the full Cost Centre tree during scoping, map each node to a Dynamics 365 Financial Dimension value (such as Department or Cost Centre), and configure the Account Structure to include the relevant dimensions. Multi-level Cost Centres become hierarchical dimension values with a parent-child structure preserved in the dimension setup.

Prowess ERP vendor records migrate to Dynamics 365 Vendor with name, address, contact, and payment terms preserved. GST registration numbers stored as custom fields in Prowess ERP map to the Tax Registration Number field on Vendor. Vendor-specific credit limits require manual confirmation post-import because Dynamics 365 enforces a separate credit limit workflow that may differ from the source practice.

Prowess ERP customer records migrate to Dynamics 365 Customer with standard address, contact, and payment terms transferred directly. Any custom customer pricing tiers or regional sales office assignments implemented as custom fields in Prowess ERP require field-level mapping; we flag these during schema discovery and pre-create the corresponding custom fields in Dynamics 365 before import.

Prowess ERP item masters carry manufacturing attributes (BOM levels, work centre assignments, unit-of-measure conversions) that are fully implementation-specific. Standard fields such as item number, description, unit of measure, and default site migrate 1:1. BOM structures and routing data migrate as item dependencies and are flagged for manual re-assembly in the Production module because BOM Editor and Route Designer in Dynamics 365 require re-entering these relationships visually rather than as flat record imports.

Open Prowess ERP Purchase Orders migrate as Purchase Order headers with line items, quantities, and prices preserved. The Prowess ERP workflow state (such as 'Planning stage' or 'Execution stage') maps to the nearest Dynamics 365 PO status; any custom status values without a direct equivalent are flagged in the mapping document and resolved by the customer's buyer during UAT. Closed and received POs migrate as historical records with a Closed status.

Open Prowess ERP Sales Orders migrate with headers, lines, pricing, and discount structures transferred. Back-ordered lines are flagged separately for confirmation before fulfilment re-entry in Dynamics 365. Custom fields added by the implementing partner require field-level mapping; we pre-create any missing custom fields in Dynamics 365 before import to avoid silent truncation.

Prowess ERP work orders migrate to Dynamics 365 Production Order with header and line structure, scheduling dates, and quantities preserved. BOM links and routing associations are extracted as dependencies and mapped to the Dynamics 365 BOM Designer and Route Designer setup files. Because manufacturing workflows differ significantly between Prowess ERP deployments, we deliver a BOM and routing re-assembly checklist rather than assuming flat-record import correctness.

Outstanding receivables and payables extract from Prowess ERP as open-invoice records with current balance, due date, and allocation status. We map these to Dynamics 365 open invoice format (CustTrans and VendTrans equivalents). Post-migration balance validation is mandatory: the customer runs a trial balance in Dynamics 365 and compares to the Prowess ERP open-balance report before go-live.

Prowess ERP user assignments use internal IDs that vary by implementation. We map users by email address as the join key. Any Prowess ERP user without a matching email in the Dynamics 365 directory goes to a reconciliation queue for the customer's IT admin to provision before record import resumes. Employee master data maps to the HcmWorker table in Finance & Operations or the Employee table in Business Central.

Every Prowess ERP deployment has unique custom fields created during implementation. We extract the full schema at scoping time using the partner-provided database export, map each custom field to a typed Dynamics 365 field (text, decimal, integer, enum, or date), and pre-create the destination schema before any data moves. This step adds one to two days to scoping but prevents silent data loss during import.

Binary document attachments stored in Prowess ERP's file system or blob storage are not accessible via a documented public API. We recommend a separate file-level migration plan using the implementing partner's direct file-system access, with documents re-attached to the corresponding Dynamics 365 records post-import. This is out of scope for the standard API-based migration and is priced as a separate engagement.