Migrate from Newton ERP Software to Infor CloudSuite Corporate

Newton ERP maintains a Chart of Accounts tied to the company profile with account codes, names, and types (Revenue, Expense, Asset, Liability). We map each account to Infor CloudSuite Industrial's cost element structure for P&L accounts and balance sheet account structure for assets and liabilities. Account codes and names migrate directly; the account type property determines which CloudSuite financial structure the record populates. We validate total debit equals total credit across the migrated COA before proceeding to transactional data.

Newton ERP Customer records carry name, GST number, address, contact info, and credit terms. Infor CloudSuite Industrial uses Business Partner records with a Type field distinguishing Customer from Supplier. We map the Newton GSTIN field to the Business Partner tax ID field, customer name to the BP name, address and contact details to the Communication and Address tabs, and credit terms to the payment terms field. Any custom fields added via Newton Forms Customization are mapped to Infor custom properties on the Business Partner form.

Newton ERP Vendor records mirror Customer records with the addition of PAN/TAN and bank details used by the Purchase module. We map vendors to Infor CloudSuite Business Partner records with Type = Supplier. The vendor PAN/TAN maps to the tax registration field, and bank details migrate to the Bank Account tab in CloudSuite. Vendor records are loaded before Purchase Orders to satisfy the supplier reference on PO header records.

Newton ERP Items include name, SKU, unit of measure, opening stock, reorder level, and valuation method. We map SKU to Item Code, item name to Item Description, and unit of measure to the UOM field. Opening stock value and quantity migrate as an initial inventory transaction in CloudSuite's inventory layer. Reorder level and valuation method (FIFO, Weighted Average) map to CloudSuite's planning and costing configuration tabs. Items are loaded before Sales Orders and Purchase Orders to satisfy item references on order lines.

Newton ERP Sales Orders link Customers to Inventory and generate accounting entries in real time. We extract the full order header (order number, customer reference, order date, status) and line items (item, quantity, rate, tax code, discount). In CloudSuite Industrial, Sales Orders are created in the Order Management module with status preserved as Order Status. Open orders migrate with their full line detail; closed orders migrate as historical records with status = Closed. We resolve the customer BP reference and item reference at migration time before inserting.

Newton ERP Purchase Orders link Vendors to Items and drive GRN (Goods Receipt Note) creation. We export PO header data and line items with vendor reference, item, quantity, rate, and delivery date. In CloudSuite, Purchase Orders are created in Procurement with Supplier BP reference resolved. We map the delivery date to the required date field and preserve the PO number from Newton as the external PO reference for traceability.

Outstanding receivables and payables in Newton ERP track invoice date, due date, open balance, and customer or vendor reference. We extract open AR as invoices in CloudSuite's Accounts Receivable module and open AP as invoices in AP module, preserving the original invoice number, amount, due date, and GST tax code. Open balances migrate as unresolved ledger entries that the customer's finance team reconciles post-migration. Closed transactions from Newton do not reopen in CloudSuite; we confirm with the customer which closed transactions to archive as historical records versus which to settle before cutover.

Newton ERP's HR module holds employee profiles, department assignments, and salary records. We export the employee master with employee number, name, department, designation, and hire date. CloudSuite HCM or the HR module within the selected CloudSuite edition receives these records. Department names from Newton map to Cost Centers in CloudSuite. If the customer uses a separate HCM system post-migration, we export employees as a standalone dataset with a cross-reference table for the customer's IT team to integrate.

Some Newton ERP customers use the Forms Customization feature to add non-standard properties to Customer, Vendor, or Item records that do not appear in standard report exports. During scoping, we audit the source tenant's active Forms views and instruct the customer to export using the specific custom-form view that captures all active fields. Each discovered custom field is then provisioned as an Infor CloudSuite custom property on the relevant form (Business Partner custom properties for customer/vendor fields, Item custom properties for inventory fields). We document the full custom field inventory as a named appendix in the migration handoff document.

Newton ERP supports document attachments at transaction and master-record level, but no public attachment export API exists. We work with the customer to obtain attached files via a vendor-assisted data extraction where available, and we map any extracted files to Infor Document Management (IDM) during migration. Where attachments cannot be reliably extracted, we flag them in the migration handoff document and recommend the customer use IDM's document association features post-load to re-attach critical files. This is a best-effort scope with explicit customer sign-off on the attachment inventory before migration begins.