Migrate from AFAS to Acumatica

AFAS Employee records map 1:1 to Acumatica Employees. Birthdate, start date, employment type, department, and manager hierarchy are preserved. AFAS user accounts are mapped to separate Acumatica user records by email match; employees without system access land as inactive users flagged for provisioning.

AFAS payroll runs have no native Acumatica equivalent — Acumatica's Payroll module handles US/CA payroll differently. FlitStack maps AFAS payroll registers as custom payroll batch records with earnings codes, deduction codes, and run dates preserved in custom fields on the Employee entity. YTD totals are reconstructed from AFAS payroll history lines.

AFAS debtors map to Acumatica Customers. Payment terms, credit limit, VAT registration, and billing address are migrated. AFAS customer-specific invoice layouts have no Acumatica equivalent — these are documented for rebuild using Acumatica's AR Invoice templates. All customer-specific settings such as language preferences and tax codes are also transferred and mapped to Acumatica's corresponding fields.

AFAS creditors map to Acumatica Vendors. Remit-to address, 1099 flag, payment method, and terms migrate directly. Multi-vendor contacts stored in AFAS contacts become Acumatica Vendor Contacts. Vendor payment hold flags and default expense categories are also imported, and any custom vendor-specific fields are mapped to Usr-prefixed custom fields on the Vendor DAC.

AFAS invoices migrate as Acumatica AR Invoices with original document dates, descriptions, line amounts, and tax amounts preserved. AFAS invoice reference numbers become Acumatica reference numbers. Status (open/paid/overdue) is mapped using Acumatica's payment/refund workflow. AFAS's project-linked invoices preserve the project association via the InvoiceDetail entity.

AFAS purchase invoices map to Acumatica AP Bills. Vendor invoice number, invoice date, description, line amounts, and tax codes transfer. AFAS's project-linked purchase invoices carry the project reference into Acumatica's BillDetails project association. Line-level discounts and tax groups are preserved, and any project assignments are carried over using Acumatica's BillDetails entity.

AFAS GL accounts map 1:1 to Acumatica GL Accounts. Account code, description, account type (Asset, Liability, Income, Expense), and active/inactive status are preserved. AFAS account hierarchies map to Acumatica's account groups. Sub-account structures and account group assignments are also imported, ensuring that reporting hierarchies replicate the AFAS chart of accounts.

AFAS journal entries migrate as Acumatica journal transactions with original posting date, batch number, description, and line items (account, debit, credit). Source module identifier is stored in a custom field for traceability. Batch descriptions and source module tags are retained, and any memo fields are transferred as custom text fields for audit purposes.

AFAS stock articles are classified as either Non-Stock Items or Stock Items in Acumatica based on AFAS's stock-control flag. Item class, warehouse location, default unit of measure, and current stock quantities transfer. AFAS's unit-of-measure conversions map to Acumatica's UOM table.

AFAS projects with task breakdowns and cost registrations map to Acumatica Projects with project tasks and cost codes. AFAS project templates become Acumatica project templates. Employee cost rates and vendor cost assignments from AFAS are preserved as custom fields on the Acumatica Project entity.

AFAS project lines with cost codes and budget amounts merge into Acumatica project tasks with cost codes. Multiple AFAS cost-code categories per project are flattened into Acumatica's cost-code schema using a value-mapping table. Budget vs. actual flags are preserved. Cost code assignments are linked to the corresponding project tasks, and any budget alerts are preserved as custom fields on the task.

AFAS contacts (people) map to Acumatica Contacts. Name, email, phone, job title, and address fields migrate directly. AFAS contact associations to customers or vendors become Acumatica Contact relationships on the parent Customer or Vendor record. Contact preferences such as mailing opt-outs and communication notes are transferred to Acumatica's Contact entity using custom fields.

AFAS extra tables (custom objects created in AFAS admin) map to Acumatica DAC objects with a Usr-prefixed name. Each extra table field is created as a custom field on the corresponding Acumatica DAC using the customization project manager. N:N relationships between extra tables require junction tables in Acumatica.

AFAS bank accounts and cash accounts map to Acumatica Cash Accounts with account number, bank name, currency, and current balance. AFAS bank reconciliation data is stored in a custom field for post-migration reconciliation. Bank reconciliation settings and any associated payment formats are imported into Acumatica's Cash Account configuration.

AFAS fixed asset records migrate as Acumatica Fixed Assets with acquisition date, cost, accumulated depreciation, useful life, and asset class. Depreciation schedules are stored as custom fields because Acumatica Fixed Asset depreciation is calculated within the Fixed Asset register. Asset maintenance schedules and insurance information are also imported as custom fields on the Fixed Asset record.