Migrate from Proteus E12ERP to Microsoft Dynamics 365 Business Central

Proteus E12ERP Customer records map to Dynamics 365 Finance and Operations Customer entities. The customer ID, name, contact details, payment terms, and credit limit transfer. Customer posting groups in Dynamics 365 must be configured before migration to set the correct posting profile for accounts receivable. Currency denomination from Proteus maps to the Customer's transaction currency; INR-based records default to the configured base currency.

Proteus E12ERP Vendor records map to Dynamics 365 Vendor entities. Vendor name, contact, payment terms, and bank details transfer. Vendor posting groups in Dynamics 365 must be configured to set the correct accounts payable posting profile. Multi-location vendor addresses map to the Vendor address structure in Dynamics 365.

Proteus E12ERP Inventory Items (SKU, description, unit cost, quantity on hand) map to Dynamics 365 Released Products. Stock quantities transfer as on-hand inventory quantities linked to the Inventory site. Unit cost becomes the current inventory cost; Dynamics 365 inventory valuation model (Standard, FIFO, Moving Average) must be configured per item before on-hand quantities are posted. Item model group and storage dimension group assignments happen in Dynamics 365 configuration before migration.

Proteus E12ERP Sales Order records with line items and status map to Microsoft Dynamics 365 Sales Order entities. Order status (open, partially received, closed) maps to the Microsoft Dynamics 365 Sales Order status enumeration. Customer references and pricing transfer; item numbers resolve to the Released Product ID. Order-level charges map to Miscellaneous charges on the Sales Order. We flag Sales Orders with partial receipt for manual review post-migration because Dynamics 365 requires posting profiles for partially invoiced orders.

Proteus E12ERP Purchase Order records with vendor references, line items, quantities, and status map to Dynamics 365 Purchase Order entities. Status (open, received, closed) maps to the Dynamics 365 Purchase Order status. Vendor ID resolves to the Dynamics 365 Vendor entity. Line item quantities transfer with delivery status flagged; inventory receipt posting requires that the receiving site and warehouse are configured in Dynamics 365 before lines are posted.

Proteus E12ERP Revenue Centers represent branches or cost centres without a standard ERP equivalent. We map each Revenue Center to a Dynamics 365 Site record (for inventory transactions) and a Financial Dimension value (for financial reporting). The dimension set is assigned to the Chart of Accounts structure in Dynamics 365. If Proteus Revenue Centers overlap in meaning with Departments, we also create a Department dimension and assign the appropriate values. The customer reviews the dimension mapping during scoping because Revenue Center naming conventions vary significantly between deployments.

Proteus E12ERP account codes and types map to Dynamics 365 Chart of Accounts with Account Type (Ledger, Expense, Revenue, Asset, Liability), Account Category, and Posting Profile. Main account numbers transfer directly; sub-account structure maps to Financial Dimension combinations. Currency denomination per account is preserved. We validate that each account type maps to a valid Dynamics 365 posting profile before import. Balance carryforward requires a separate year-end close process in Dynamics 365 after migration.

Proteus E12ERP open invoice state (unpaid purchase orders and outstanding vendor liabilities) is not documented as an exportable object. We cannot guarantee completeness of open-AP records from the source export. We flag this explicitly and recommend that the customer's finance team manually creates open vendor transactions in Dynamics 365 Accounts Payable after migration, referencing the original Proteus PO number and vendor statement. This is a manual step outside the automated migration scope.

Proteus E12ERP open invoice state (outstanding customer invoices and receivables) is not documented as an exportable object. We cannot guarantee completeness of open-AR records from the source export. We flag this explicitly and recommend that the customer's finance team manually creates open customer transactions in Dynamics 365 Accounts Receivable after migration, referencing the original Proteus invoice number and customer statement. This is a manual step outside the automated migration scope.

Pricing rules attached to Sales Orders or Purchase Orders in Proteus E12ERP may exist as customer-specific or vendor-specific price lists. We extract these as separate price agreement records and map them to Dynamics 365 Trade Agreements (price and discount journal lines). Price types are assigned (Purchase Price or Sales Price) and the applicable item, vendor, or customer is linked. If Proteus pricing is embedded in order lines rather than a master price list, we reconstruct trade agreements from order history.

Proteus E12ERP Customer records may include contact-level detail (primary contact name, phone, email). These map to Dynamics 365 Contact records linked to the Customer entity. Multiple contacts per customer map to separate Contact records with the Customer as the parent. Contact purpose and role are preserved as Contact fields. We do not migrate the CRM activity history embedded in the Proteus CRM module as engagements; the activity model in Dynamics 365 Finance and Operations differs significantly from the CRM activity timeline.

Proteus E12ERP Vendor records include contact-level detail. These map to Dynamics 365 Contact records linked to the Vendor entity. Primary contact information transfers; additional contacts create separate Contact records with the Vendor as the parent. Contact details (phone, email, address) are preserved. Vendor-sourced purchase communication history does not migrate as activities in Dynamics 365 Finance and Operations because the activity model differs from CRM-oriented systems.