Migrate from R4 ENTERPRISE to Acumatica

R4 Enterprise stores customer records with a flat property list including credit limit, payment terms, and currency. Acumatica Business Accounts hold the same core fields. The Acumatica CustomerClass determines defaults for payment terms and billing address rules — FlitStack maps R4 Enterprise customer classes to Acumatica CustomerClasses during migration. Any custom properties on the R4 Enterprise customer record become Acumatica Attributes on the Business Account.

R4 Enterprise vendor master holds name, payment terms, tax ID, and AP account assignment. Acumatica Vendors use the same structure. Payment Terms on the vendor record are stored as a pick-list value — FlitStack performs a value-by-value map between R4 Enterprise terms (e.g., Net 30, 2/10 Net 30) and the Acumatica Payment Terms list. Tax ID migrates as-is; 1099 flag maps to the Acumatica VendorTaxZone ID.

R4 Enterprise holds item-level inventory with optional per-warehouse quantities stored as a warehouse flag on the item. Acumatica separates Stock Items (the product definition) from Quantities (per-Warehouse and Location). FlitStack maps the R4 Enterprise item record to an Acumatica Stock Item, then creates Quantity records for each R4 warehouse location. Unit of Measure on the item maps to Acumatica's UOM class. Lot/Serial tracking requires Acumatica Lot/Serial class configuration before migration — FlitStack delivers a pre-migration schema checklist for this.

R4 Enterprise uses a single-segment account code with subaccounts encoded as dash-delimited segments (e.g., 1100-001). Acumatica COA uses a separate Account code plus optional Dimension segments. FlitStack maps the R4 Enterprise account code to the Acumatica Account field and preserves the subaccount segment as a custom User-Defined Field (UDF) on the account unless Acumatica Dimensions are configured. If the customer uses Dimensions, FlitStack maps subaccount segments to the corresponding Dimension values during migration planning.

R4 Enterprise stores AR invoices as header records with line items in a child table. Acumatica uses the same header-detail model. FlitStack creates the AR Invoice header using the customer account lookup, then inserts line items referencing the Stock Item or GL account. Invoice date, due date, and total amount migrate as direct fields. The R4 Enterprise payment status is preserved as a custom field on the invoice so the Acumatica team can decide whether to post open invoices or historical closed ones.

R4 Enterprise AP invoices map directly to Acumatica AP Bills. Flumatica Bill header maps to the R4 invoice header; line items map to Bill Details. Vendor lookup uses the Acumatica VendorID resolved during the vendor migration phase. Payment Terms on the bill come from the vendor record in Acumatica — FlitStack verifies vendor records are migrated first so the vendor reference resolves. Any R4 Enterprise discount terms are stored as a custom field if Acumatica's standard terms do not cover the same values.

R4 Enterprise uses subaccount segments to classify transactions by department, cost center, or project. In Acumatica, this is the Dimensions framework (available in advanced editions). If Dimensions are not configured, FlitStack maps subaccount codes to a custom UDF on the Account or Project record — Acumatica Dimensions can be activated post-migration and the subaccount UDF data moved into them. FlitStack delivers the subaccount-to-Dimension mapping plan before the migration runs so the Acumatica admin can pre-configure Dimensions.

R4 Enterprise lot and serial numbers are stored as item-level flags or attributes. Acumatica requires a Lot/Serial class to be configured on the Stock Item before lot/serial tracking activates. FlitStack identifies every R4 Enterprise item with lot or serial tracking, delivers the Lot/Serial class configuration checklist for each item, and then migrates the lot numbers and expiration dates as Lot/Serial records linked to the Stock Item after the class is configured.

R4 Enterprise production orders contain the item to manufacture, BOM reference, routing, and quantities. Acumatica Manufacturing Edition holds Production Orders with a separate BOM and Routing structure. FlitStack maps the R4 Enterprise work order to an Acumatica Production Order header and stores the BOM and routing references as custom UDF fields. Full BOM/routing structure migration requires Acumatica Manufacturing Edition configuration — FlitStack delivers a BOM mapping plan with the production order records so the manufacturing setup can be completed in parallel.

R4 Enterprise stores attachments on records in its own file store. Acumatica has no native document management equivalent — files attach to individual records via the Files entity. FlitStack re-uploads R4 Enterprise file attachments to the corresponding Acumatica record (Customer, Vendor, Stock Item, etc.) using the Files API. Original file names and upload dates are preserved in the Acumatica file metadata. Any custom metadata stored alongside files in R4 Enterprise is preserved as a custom Note attached to the same record.

R4 Enterprise custom properties are named fields stored directly on each record. Acumatica stores equivalent data as Attributes linked to a screen-specific Attribute Group. FlitStack identifies every custom property in R4 Enterprise, maps it to an Acumatica Attribute on the matching screen (e.g., Customers screen for customer attributes), and delivers the Attribute Group setup checklist. If the same custom property appears on multiple record types in R4 Enterprise, FlitStack creates separate Attributes for each Acumatica entity to preserve the same data context.

R4 Enterprise user records contain login name, email, and role. Acumatica Contacts are linked to Business Accounts or exist as standalone user records. FlitStack maps R4 Enterprise users with login access to Acumatica system users and non-logging contacts (e.g., purchasing contacts) to Contact records linked to the appropriate Business Account. Email addresses are matched between systems to resolve duplicates when the same person appears as both a user and a contact in R4 Enterprise.