Migrate from Proteus ERP to Microsoft Dynamics 365 Business Central

Proteus ERP Customer records store contact data, buying habits, and referral source in a single entity. We split this into Microsoft Dynamics 365 Contact (person-level) and Account (organization-level) records, using the customer type flag in Proteus to determine whether the record lands as a Person or Company Account. Address, phone, and email fields map directly; referral source becomes a custom Account field for segmentation.

Proteus ERP Vendor master records map directly to Dynamics 365 Vendor records. Vendor code in Proteus becomes the Vendor Number in Business Central or the Vendor Account in Finance and Operations. We handle code collision detection during scoping — if the destination already has vendor records with overlapping codes, we apply a prefix strategy and document it in the mapping table before any write operations.

The Proteus ERP accounting module uses a GST-compliant Chart of Accounts with segment lengths and naming conventions that may differ from the destination COA. We build a mapping table during the discovery phase that aligns each Proteus account code to its Dynamics 365 G/L Account number, assigns the correct Account Type (Posting, Heading, Total), and maps GST tax codes to Dynamics 365 Tax Group configurations. Balance carryforward from the Proteus COA is handled as an opening balance entry in the destination.

Proteus ERP Items with SKU, description, stock levels, pricing tiers, and revenue center assignments map to Dynamics 365 Items. We preserve multi-revenue-center flagging as inventory posting groups in Business Central or warehouse management configuration in Finance and Operations. Stock quantities transfer as opening inventory quantities on hand at the valuation method (Standard or Average) configured in the destination. Product costing version and GST/HST posting group assignment happens during the item migration phase.

Open and historical Sales Orders carry header-level fields (order date, customer reference, shipping address) and line-level fields (item number, quantity, unit price, discount). Line item mapping requires resolving each Proteus item code to the Dynamics 365 Item Number created during the item migration phase. We import open orders first to allow the business to continue processing, then import historical orders in date-range batches to manage file size. Order totals and tax amounts are validated against the source before closing the order in the destination.

Purchase Orders in Proteus ERP are tracked with vendor associations and line items. We preserve the PO-to-receive linkage by mapping vendor PO numbers to the Dynamics 365 Purchase Order Number and linking the vendor account. Line items resolve item codes to the destination item numbers and carry forward quantity ordered versus quantity received as open receipt lines in Dynamics 365.

Proteus ERP Invoice records include GST/HST data, payment terms, and posting status. We map posted invoices to the corresponding Dynamics 365 Posted Sales Invoice or Posted Purchase Invoice, and open (unposted) invoices to Sales Invoice or Purchase Invoice drafts. Historical invoices may require date-range scoping based on export file sizes; we recommend migrating the most recent 24-36 months of posted invoices and archiving older records in a read-only reference store per ERP migration best practices.

Proteus ERP Employee records map to the Dynamics 365 Human Resources Worker entity. We map employee ID, name, address, employment status, department, and job title. Compensation and benefit data migrates as historical employment records where the destination supports them. User provisioning for Dynamics 365 access requires separate Active Directory or Azure AD integration, which we coordinate with the customer's IT team as a parallel workstream.

Proteus ERP e-commerce orders are integrated into the back-end system with inventory synchronization. We pull order data and line items and map them to Microsoft Dynamics 365 Sales Order records, tagging them with a custom e-commerce source identifier so that the customer can filter reporting by sales channel. Order totals and tax amounts are validated against the source before import completion.

POS transactions in Proteus ERP are captured within the same inventory and accounting system. We extract transaction-level data — transaction date, tender type, line items, and totals — and map them to Microsoft Dynamics 365 Sales Invoice lines or General Journal lines depending on whether the destination uses the Retail POS module (Dynamics 365 Commerce) or a standalone Business Central setup. Tender type maps to payment method codes in the destination.

Custom fields added within Proteus ERP's CRM or accounting modules may not appear in the default export view. We identify custom field columns during the scoping call, request a full field export that includes them, and then create matching User-Defined Fields in Dynamics 365 Business Central or extended fields in Finance and Operations before importing data. Custom field type mapping (text to text, number to decimal, date to date) is documented in the mapping table.

Proteus ERP uses multi-revenue-center assignments that tag each inventory transaction with a revenue center. Dynamics 365 does not have a native revenue center concept; we map each Proteus revenue center to a combination of Location Code (for warehouse assignment) and Inventory Posting Group (for G/L posting destination) in Business Central, or to a Warehouse ID with a corresponding Financial Dimension in Finance and Operations. This mapping is built as a configuration table before any inventory data is written.