Migrate from MONITOR ERP to Acumatica

Monitor Customer maps to Acumatica Customer. Monitor's parent-child hierarchy maps to Acumatica's Location hierarchy where the top-level Customer is the parent and each Monitor subsidiary or branch address becomes an Acumatica Location. Credit limits and payment terms from Monitor Customer carry forward as Acumatica Customer Class settings and payment term codes.

Monitor Vendor maps to Acumatica Vendor. Payment methods and bank account details transfer as Acumatica Vendor attributes. Multi-bank payment configurations in Monitor map to Acumatica's payment method selection per vendor. Each vendor's default payment terms and currency settings also map to the corresponding Acumatica vendor fields for smooth invoice processing.

Monitor Item classified as stock item maps to Acumatica Stock Item. Monitor's unit of measure conversions, lot/serial number settings, and default warehouse locations carry forward. Valuation method (standard, average, FIFO) maps to Acumatica's Inventory Valuation Method field per item class.

Monitor Items without inventory tracking (services, materials, charges) map to Acumatica Non-Stock Items. They are available for use on Purchase Orders and Sales Orders without inventory receipts. These items can be assigned default unit costs, vendor defaults, and item classes, and they appear in Acumatica's item lookup across all order screens.

Monitor Sales Order maps to Acumatica Sales Order with line items referencing Stock or Non-Stock Items. Monitor order statuses (Quote, Confirmed, Invoiced) map to the corresponding Acumatica Sales Order statuses via a value-mapping table. Order dates, due dates, and customer references preserve original values for reporting continuity. Each line item carries the original unit price and tax amount, and any Monitor discounts are transferred as Acumatica line discounts.

Monitor Purchase Order maps to Acumatica Purchase Order. Vendor, line items, and terms transfer directly. Monitor's purchase approval workflow does not migrate — it must be rebuilt in Acumatica's approval map configuration. Additionally, any custom fields attached to the Monitor PO are translated to Usr-prefixed custom fields in Acumatica for the Purchase Order screen.

Monitor Work Order is a discrete manufacturing entity. It maps to Acumatica Manufacturing Order with material issues and labor tracking. Monitor operation routing (work centers, sequence, estimated time) transfers as AM Operation records. If Monitor Work Orders are linked to Sales Orders, the link is preserved via Acumatica's Project and Production Order association.

Monitor BOM maps to Acumatica BOM with component lines and quantities per BOM version. Multi-level BOMs flatten or preserve hierarchy depending on Acumatica configuration. Phantom BOMs map to Acumatica's Phantom BOM checkbox. The component operations, work centers, and routing steps also transfer as sub-records within the BOM definition.

Monitor GL Accounts map to Acumatica Account records using AccountCD. Monitor's Swedish account number structure maps to Acumatica's account segment. Subaccounts for cost centers, departments, or projects map to Acumatica Subaccount dimensions configurable in the GL Setup screen. The mapping also preserves any inactive flag and tax settings for each account.

Monitor Contact linked to a Customer maps to Acumatica Contact with the CustomerID lookup established. Monitor contact roles (Buyer, Approver) map to Acumatica Contact Class-based roles. Multiple Monitor contacts per customer collapse to individual Acumatica Contact records all pointing to the same CustomerID.

Monitor inventory adjustments, receipts, and issues map to Acumatica Inventory Receipts and Issues. Original transaction dates and warehouse IDs preserve. For Monitor transactions linked to Work Orders, the link transfers as a reference on the corresponding AM Production Order. All adjustments also retain the source document number for audit trail.

Monitor custom fields on any register map to Acumatica custom fields with the Usr prefix (e.g., UsrPersonalID for a Monitor Personal ID field). Custom fields require an Acumatica Customization Project to be published before the migration runs — we deliver this project as part of the schema setup plan.