Migrate from Newton ERP Software to Microsoft Dynamics 365 Business Central

Newton ERP maintains a COA tied to the company profile with account codes, names, and types (Revenue, Expense, Asset, Liability). We extract every COA entry and map each to the destination chart using the account category and subcategory matching the Indian chart of accounts structure. GST-related accounts (Input Tax, Output Tax, TCS, TDS) map to Tax Posting Setup in Business Central or Tax Group configuration in Finance. Account numbers and names are preserved; posting groups are assigned during configuration based on account type.

Newton ERP stores a single company profile (GST number, address, logo, financial year settings) as the organizational root. We extract the full profile and configure Business Central's Company Information or Finance's Legal Entity record to match, including GST registration number, address, and tax registration details. If multiple companies are in scope, each company profile becomes a separate Legal Entity in Dynamics 365.

Newton ERP Customer records carry name, GST number, address, contact info, and credit terms. Some implementations include custom fields added via Forms Customization. We extract all standard fields plus any active custom form view fields, map GSTIN to the Tax Identification Number field, and preserve credit limit and payment terms. Customers are loaded before any Sales Orders to satisfy the downstream lookup on the sales documents. Customer addresses use the Incoming Document mechanism or direct address fields depending on the Dynamics 365 version.

Vendor records mirror Customer records with the addition of bank details and PAN/TAN. The vendor list drives Purchase Order generation and GRN creation in Newton ERP. We preserve the full vendor record including payment terms, GSTIN, PAN, and bank account details. Vendors are loaded before Purchase Orders and before any open AP extraction so that the vendor reference is resolved at migration time.

Items include name, SKU, unit of measure, opening stock, reorder level, and valuation method. Newton ERP tracks stock in real-time via the Inventory module. We export the item master and current stock quantities, map valuation method (FIFO, Weighted Average, Standard) to the corresponding Dynamics 365 costing method, and populate the Inventory Posting Setup for each item location. Items are loaded after the Chart of Accounts because inventory accounts must exist before items can be posted.

Sales Orders link to Customers and reduce inventory in Newton ERP. Open and closed orders both carry line items with quantity, rate, tax, and discount. We export full line-item detail and order status. Open orders (not yet invoiced) migrate as Sales Orders in Business Central; orders already billed migrate as posted Sales Invoices with the invoice number preserved. Closed orders that are fully fulfilled but not yet invoiced are converted to invoices before migration. Line items map unit price, quantity, discount, and tax amount to corresponding Microsoft Dynamics 365 Sales lines.

Purchase Orders link to Vendors and drive GRN (Goods Receipt Note) creation. We export PO header data and line items, mapping vendor references to the destination's vendor records. Open Purchase Orders migrate as Purchase Orders; closed POs with receipts already posted migrate as posted Purchase Invoices. GRN records (if tracked as separate documents in Newton ERP) are handled as posted receipt lines attached to the corresponding Purchase Order.

Outstanding receivables are tracked in the Accounts module and updated as invoices and payments are recorded. We extract the open balance, invoice date, due date, and original invoice reference for each open AR entry. Open AR migrates as open customer ledger entries in Business Central using the Move Cards functionality or direct posting journals. The original invoice number is preserved in the Document No. field and the remaining amount in the Open field for reconciliation in the destination system.

Outstanding payables are tracked in the Accounts module. We extract the open balance, invoice date, due date, vendor reference, and original invoice number for each open AP entry. Open AP migrates as open vendor ledger entries using the same journal-based posting approach as AR. The customer validates outstanding payables against vendor statements after migration.

The HR module holds employee profiles, salary slips, and hiring records. Employee numbers and department assignments vary between implementations. We export the employee master, including employee number, name, department, designation, date of joining, and salary information. Employee data loads after the Chart of Accounts (for salary expense account mapping) and after any department records. If Newton ERP stores salary history, we preserve it in a custom Pay History table in Dynamics 365 unless the HR module is licensed separately.

Newton ERP Forms Customization adds non-standard properties to Customer, Vendor, or Item records that do not appear in standard report exports. We audit the source tenant's active forms during scoping, list every custom field with its data type, and create equivalent custom fields in Dynamics 365 before the relevant record import. The customer exports using the specific custom form view that captures all active fields, and we apply those values to the mapped custom fields during load.

Newton ERP supports document attachments at transaction and master-record level, but the CSV provides no evidence of a public attachment export API. We cannot guarantee reliable bulk attachment extraction from this platform. We do not migrate attachments as a standard scope item. We flag the attachment count visible in the Newton ERP UI and provide a written recommendation for the customer to manually migrate critical documents post-cutover, or to use the Dynamics 365 SharePoint or OneDrive integration to re-associate documents after the migration.