Migrate from eBIZ SMARTZ Business ERP to Acumatica

eBIZ SMARTZ account codes map to Acumatica GL Accounts when the source account structure uses a consistent segment delimiter. Account type (Asset, Liability, Equity, Revenue, Expense) maps to the Account Type dropdown in the COA screen (GL104000). Active/inactive status preserved as the Account Status field.

eBIZ SMARTZ multi-level cost centers (Category > Cost Center > Sub-Cost Center) collapse into Acumatica's dimensional model. Option A: map to the Location dimension (IN102000) for operational cost centers. Option B: map to the Project dimension (PM301000) if source cost centers represent project attributions. FlitStack surfaces the mapping decision before migration.

Customer name, short name, address, contact details, tax ID, and credit terms map directly to the AR Customer record. Opening balance invoices (unpaid invoices at migration date) load as Open AR Documents with reference to the original voucher number stored in UsrOriginalVoucherNbr__c. Customer class from eBIZ SMARTZ maps to Acumatica's Customer Class field.

Vendor master records carry over with name, address, contact, tax registration, and payment terms. Opening balance bills (unpaid bills at migration date) import as Open AP Documents with original voucher reference stored in UsrOriginalVoucherNbr__c. Vendor class maps to Acumatica's Vendor Class.

Posted sales invoices from eBIZ SMARTZ become locked AR Invoices in Acumatica. Invoice number, date, customer, line items, tax amount, and total map to AR301000. Status is set to Open or Closed based on payment status in source. Currency defaults to the company's base currency.

Posted purchase invoices become AP Bills in Acumatica (AP301000). Vendor, invoice date, line items, tax, and total carry over. Open bills retain original invoice reference in UsrOriginalVoucherNbr__c. Closed bills import as paid if a matching payment voucher exists in source.

Cash receipt and payment vouchers from eBIZ SMARTZ map to Cash Management entries in Acumatica (AR202000 or AP202000). The original voucher number is stored in UsrOriginalVoucherNbr__c for reconciliation. Payment method, account, date, and amount transfer directly. Cash management settings are configured in CA202000 to support bank reconciliation and payment processing workflows.

Bank accounts defined in eBIZ SMARTZ create Cash Accounts in Acumatica (CA202000). Bank name, account number, bank code, and currency map to CA202000. Reconciliation settings and payment method links are configured in the Cash Account screen. Bank-specific preferences, including payment processing integration and statement import rules, are re-established in Acumatica's cash management configuration.

eBIZ SMARTZ budget versions per period map to Acumatica Budget records (GL403000). Budget lines attach to GL accounts and optionally to the Project or Location dimension for multi-dimensional allocation. Period allocation (monthly, quarterly, yearly) is re-specified in Acumatica's budget setup. Budget validation rules and override permissions are configured during the migration to match the source control requirements.

Customer debit notes map to AR Memos (AR301000, type = Invoice). Customer credit notes map to AR Credit Memos (AR301000, type = Credit Memo). Vendor debit and credit notes map to AP Bill Adjustments. Original voucher reference preserved in UsrOriginalVoucherNbr__c for audit traceability and source document lookup.

eBIZ SMARTZ multi-level voucher approval workflows have no direct Acumatica equivalent. Approval conditions, threshold amounts, and approver hierarchies are exported as a JSON reference document for the Acumatica administrator to rebuild in SM302000. The exported file documents the approval chain logic so it can be recreated as Approval Maps in the destination system.

eBIZ SMARTZ financial reports and dashboards are not migrated. FlitStack exports the report definitions, filter criteria, and column layouts as reference files. Acumatica's Report Designer (SQ302000) and Generic Inquiries (SM208000) are used to rebuild equivalent reports. The exported reference files guide the reconstruction of each report with its original parameters and data sources.