Migrate from Tranquil ERP to Microsoft Dynamics 365 Business Central

Tranquil ERP's account hierarchy maps to Microsoft Dynamics 365 Business Central or Finance and Supply Chain Management's Chart of Accounts structure. We extract the full account code, account name, account type (General, Post to General Ledger, and account category), and any hierarchy parent references. Dynamics 365 enforces a structured account code format that may require padding or re-segmenting legacy codes. Inactive or duplicate account codes from Tranquil ERP are flagged during the data audit pass and consolidated before import to prevent posting errors in Dynamics 365.

Tranquil ERP customer records map to Dynamics 365 Customer records. We extract customer name, address, payment terms, currency, tax registration number, and any open AR balance references. Dynamics 365 Business Central supports Customer Posting Groups that map to the general ledger; we configure these during schema setup. The customer's country/region determines the default tax jurisdiction setup in Dynamics 365. Open invoices and credit memos are migrated as separate ledger entries attached to the customer record.

Tranquil ERP vendor master records map to Dynamics 365 Vendor records with contact details, bank account information, payment terms, and Vendor Posting Group assignments. We preserve the vendor's purchasing transaction history and map any open purchase order balances to AP ledger entries in Dynamics 365. Vendor-specific tax information (TDS/TCS for Indian compliance) maps to the corresponding tax group configuration in Business Central or Finance and Supply Chain Management.

Tranquil ERP items with serial/batch numbers, expiry dates, and multi-UoM configurations map to Dynamics 365 Item records. The primary UoM from Tranquil becomes the Item's base UoM; any alternate UoM entries are created as Item Unit of Measure records with conversion factors. Inventory posting groups and valuation methods (Standard, FIFO, Average) from Tranquil ERP map to the corresponding inventory posting setup in Dynamics 365. Items flagged as Stocked, Service, or Non-Stock in Tranquil map to the Item Type field in Dynamics 365.

Open Purchase Orders from Tranquil ERP migrate to Dynamics 365 Purchase Orders with vendor references, line items (item number, quantity, unit cost, line discount), and current status. We resolve the vendor lookup by matching vendor code to the Dynamics 365 Vendor record created in the vendor migration phase. Closed and completed purchase orders are migrated as historical purchase archive records with a Posted status flag to preserve the transaction ledger without allowing further modification. PO approval workflows from Tranquil ERP are not migrated as code; they appear in the automation inventory document for the customer's admin to rebuild in Power Automate or Dynamics 365 workflow configuration.

Open Sales Orders migrate to Microsoft Dynamics 365 Sales Orders with customer references, line items, pricing, and shipment status. The customer account lookup is resolved from the Customer migration phase. Pricing (unit price, discounts, taxes) migrates with the order header and line structure intact. Completed sales orders are archived as posted sales invoices or historical records depending on whether they were invoiced in Tranquil ERP. Order-to-cash workflow automations from Tranquil ERP are documented in the automation inventory for the customer's admin to rebuild in Dynamics 365's sales order workflow configuration.

Current inventory quantities, warehouse assignments, serial/batch numbers, and expiry dates from Tranquil ERP map to Dynamics 365 warehouse locations and stock entry records. We extract the current stock ledger (item number, warehouse code, location, quantity, serial or batch number, expiry date) and write it to the Inventory Setup and the Item Tracking Lines in Dynamics 365 Business Central or the Warehouse Management module in Finance and Supply Chain Management. The destination's warehouse mapping is configured during schema setup, with each Tranquil ERP warehouse mapped to a corresponding Dynamics 365 location code. Reorder points and safety stock levels migrate as Item Reorder Policy settings.

Tranquil ERP employee records (personal data, roles, compensation history) map to Dynamics 365 Human Resources workers if the customer licenses the Human Resources module, or to the Employee table in Business Central Essentials. Effective-dated compensation fields migrate as Employment History records. The destination edition determines the available HR schema: Business Central Employee supports basic HR data; Dynamics 365 Human Resources (a separate product) supports benefits, leave management, and performance. We confirm the target module during scoping and adjust the HR migration scope accordingly.

Tranquil ERP custom fields on business objects (Customers, Items, Purchase Orders, Sales Orders) are detected during discovery and mapped to Dynamics 365 custom fields created via the Extension framework. In Business Central, custom fields are added via AL extensions; in Finance and Supply Chain Management, they are added via the customization layer. We preserve the original field label and data type, apply any required transformation (date format normalization, decimal precision alignment), and validate that Dynamics 365's field length does not truncate the source value. Custom field migration is validated per object during the sandbox pass before production.

Open and historical purchase invoices from Tranquil ERP map to Dynamics 365 purchase ledger entries. Posted invoices become closed vendor ledger entries; open invoices remain as outstanding payables. The vendor code lookup is resolved from the vendor migration phase. Invoice-level detail (line items, taxes, payment terms) migrates to the Dynamics 365 purchase invoice journal. TDS/TCS deductions recorded in Tranquil ERP map to the corresponding tax adjustment functionality in Business Central or Finance and Supply Chain Management.

Open and historical sales invoices migrate to Dynamics 365 customer ledger entries. Posted invoices become closed AR records; open invoices remain as outstanding receivables. Invoice header details (customer, invoice date, due date, payment terms) and line items (item, quantity, unit price, tax) migrate to the Microsoft Dynamics 365 Sales invoice journal. The customer lookup is resolved from the customer migration phase. Any finance charges or credit memos attached to invoices in Tranquil ERP migrate as separate credit memo records.

If the Tranquil ERP migration scope includes manufacturing data, Bills of Materials and routing information map to Dynamics 365 Finance and Supply Chain Management's production control module (Business Central's manufacturing features require the Premium tier). BOM lines map to production BOM lines with item numbers, quantities per, and scrap percentages. Routing operations map to work centers and machine centers with setup and run times. We verify that the destination's manufacturing edition is licensed before including these objects in the migration scope.