Migrate from Freespace ERP to Acumatica

Freespace customers map 1:1 to Acumatica BusinessAccount records classified as Customer. Primary billing address and shipping address from Freespace become the default Location on the BusinessAccount. Payment terms and credit limit from Freespace transfer to the BusinessAccount's CreditLimit and PaymentRules fields.

Freespace vendors map to Acumatica BusinessAccount records classified as Vendor. Tax registration IDs from Freespace map to the TaxRegistrationID field on the Vendor record. The 1099 vendor flag from Freespace translates to VendorTaxZone settings in Acumatica, where the tax zone determines reporting requirements. Payment terms and remittance addresses also migrate to the corresponding Vendor location fields.

Freespace inventory items map to Acumatica InventoryItem with class-group alignment. Item type (stock vs. non-stock vs. service) maps to the ItemType field. Base unit of measure from Freespace translates to the DefaultVolumeUOM/DefaultWeightUOM on the item. Valuation method selection requires explicit mapping per Freespace item class.

Freespace flat account codes require segmentation for Acumatica's dimension model. We analyze the Freespace account code pattern and propose a segment split (e.g., branch/department/account) to align with Acumatica's SubCD + Branch structure. Accounts that cannot segment cleanly are flagged for consolidation or sub-account creation.

Freespace AR invoices map to Acumatica ARInvoice records preserving the original document date, invoice number, description, and reference Nbr. Line items map to ARTran with inventory ID lookup and tax amount from Freespace redistributed via Acumatica's TaxCategory. Status (open/closed) maps to ARDocumentStatus.

Freespace AP bills map to Acumatica APInvoice records with original vendor reference number and invoice date preserved. Line items map to APTran with account distribution matching the Freespace expense coding. Prepayments and credit memos from Freespace map to APDocument with DocType discriminating between Invoice, CreditMemo, and Prepayment. Vendor-specific payment terms from Freespace transfer to the TermsID field on the APInvoice record.

Freespace sales orders map to Acumatica SOOrder with order number, date, and customer reference preserved. Line items map to SOLine with warehouse and site assignment from Freespace's default fulfillment location. Freespace shipping terms and carrier info migrate to SOOrder.ShipVia. Order hold status and discount schedules from Freespace translate to corresponding SOOrder fields and SalesPrice records.

Freespace purchase orders map to Acumatica POOrder. Vendor and buyer assignment from Freespace transfers to POOrder.VendorID and POOrder.EmployeeID. When the EmployeeID from Freespace has no match in Acumatica, we create a placeholder employee record or map to a default buyer ID to maintain referential integrity. Expected receipt date and term details from Freespace become the POOrder.ExpectedDate and POOrder.VendorLocation mapping.

Freespace contact records attached to a customer or vendor merge into two Acumatica records: a Contact record for personal details (name, email, phone) and a BusinessAccountContact junction linking to the BusinessAccount with a specific role (billing, shipping, primary buyer). Multiple Freespace contacts on one account become multiple BusinessAccountContact rows.

Freespace stores custom properties as free-form key-value pairs on standard objects. Each Freespace custom property requires a corresponding Acumatica extension field (UsrFieldName) created via the Customization Project editor before migration. Data type from Freespace (text, number, date, boolean) determines the Acumatica field type.

Freespace price list entries for an item map to Acumatica SalesPrice records keyed by customer class and quantity break. Effective dates from Freespace become the SalesPrice.StartDate/EndDate. Volume discount tiers in Freespace translate to separate SalesPrice rows per quantity tier. Where Freespace uses a specific currency, we apply the appropriate CuryID on the SalesPrice record. Price overrides at the customer level become separate SalesPrice entries linked to that specific BusinessAccount.

Freespace warehouse records map directly to Acumatica Warehouse entities with their warehouse ID and description preserved. Each Freespace bin or storage location maps to a Location record under the corresponding Warehouse, with location code and bin code transferred. Default fulfillment warehouse from Freespace becomes the primary SiteID on SalesOrder lines, ensuring orders route to the correct shipping location automatically.

Freespace tax codes map to Acumatica TaxCategory on lines and TaxZone on the BusinessAccount. Tax rate values from Freespace require value-by-value mapping to Acumatica TaxDetail rates because the underlying tax agency and jurisdiction references differ between platforms. We create a tax mapping table during the schema inventory phase, mapping each Freespace tax code to the corresponding Acumatica TaxCategory ID and TaxZone combination.

Freespace payment terms (Net 30, Net 60, 2/10 Net 30) map directly to Acumatica Terms records where the name and day count match. Custom Freespace terms with unusual day counts require new Terms records created in Acumatica before invoice migration.

Freespace item categories map to Acumatica ItemClass records for shared attributes including valuation method, posting accounts, and tax category. We create the ItemClass first, defining the default posting accounts for inventory, COGS, and revenue. Freespace's product manager assignment becomes the ProductManagerID on the InventoryItem after the ItemClass is established. Items without a designated product manager in Freespace receive a default ProductManagerID or are flagged for manual assignment post-migration.