Migrate from daftra to Acumatica

Daftra clients map to Acumatica's BAccount base class with ARCustomer extension. Acumatica requires a CustomerClass to be assigned at import time — we pre-create a default class or use your existing CustomerClass configuration. Daftra's client-level custom fields attach as Ext DAC Usr fields on BAccount. Primary contact maps to Contact DAC with ContactClass assignment.

Daftra vendors map to Acumatica's BAccount base class with APVendor extension. VendorClass assignment follows the same pre-creation logic as CustomerClass. Daftra vendor-level custom fields map to Usr fields on BAccount. Primary vendor contact maps to Contact DAC with IsActiveContact flagged. Payment terms from Daftra map to Acumatica's Terms DAC.

Daftra stocked products map to Acumatica InventoryItem with ItemClass pre-assigned. Stock item attributes — unit of measure, description, base unit, and last unit price — map directly. Daftra product custom fields (e.g., size, color) map to Usr fields on InventoryItem. We pre-create ItemClass records in Acumatica based on Daftra product categories before importing items.

Daftra services and non-stocked products map to Acumatica Non-StockItem (InventoryItem with IsStockItem = false). Description, base unit, and default unit price transfer. Tax category assignment on Acumatica's Non-StockItem requires a tax-zone mapping from Daftra's tax configuration. Unit of measure defaults to Each if no match exists.

Daftra invoices with status Open map to Acumatica ARInvoice with Release = false so they land in AR304000 as pending documents. Invoice lines map to ARTran with InventoryID, Quantity, UnitPrice, and DiscAmt. Daftra's installment invoices become separate ARInvoice records linked by reference. Tax amounts from Daftra map to Tax Category and Acumatica calculates tax on release — or we bypass with tax override if tax code mapping is ambiguous.

Daftra quotes map to Acumatica SalesOrder SO301000 in Hold status. Quote lines map to SOLine with the same inventory and pricing logic as invoice lines. If Daftra quotes have expiry dates, we populate the RequestDate and CancelDate on the SalesOrder header. Quote-to-order conversion history does not transfer — Acumatica requires manual conversion or Business Event automation post-migration.

Daftra bills map to Acumatica APBill with Hold = true so documents land in AP302000 as unreleased. APBill lines map to APTran with VendorRefNbr populated from Daftra's bill reference. Tax amounts from Daftra require mapping to Acumatica tax codes by vendor tax category. Prepayments and retainers from Daftra bill records surface as AP Payment applications on release.

Daftra client payments map to Acumatica CashSale for deposits or Payment application against ARInvoice. Payment method, amount, reference number, and date transfer. Acumatica requires the linked Customer and ARInvoice to exist before applying payments — our sequencing ensures master data lands first. Currency and exchange rate from Daftra map to Acumatica CuryID and CuryRate.

Daftra employee records map to Acumatica EPEmployee with attributes: EmployeeID, FirstName, LastName, Email, Department. Daftra salary and compensation fields map to custom Ext DAC fields — Acumatica does not store payroll amounts in the core Employee DAC without the Payroll module. Time-off balances from Daftra require custom fields on EPEmployee since Acumatica's time-off tracking uses Attendance management.

Daftra memberships, points, and loyalty credits have no native Acumatica equivalent. Points balances migrate as custom numeric fields on BAccount (UsrPointsBalance__c) and membership tiers as a custom pick-list (UsrMembershipTier__c). Acumatica's CRM Campaign entity can track engagement but not loyalty economics — your team rebuilds loyalty rule logic in Acumatica workflows.

Daftra work orders and booking records map to Acumatica's Field Service module's ServiceOrder DAC if the FS module is licensed, otherwise to a custom SOOrder extension. Work order statuses map to Acumatica status codes. Original Daftra work order IDs are preserved as UsrSourceWorkOrder__c for traceability.

Daftra custom fields per module require an Acumatica Customization Project with Usr-prefixed fields on the target DAC. We generate the project XML as part of the migration plan — your Acumatica admin publishes it before data import. Custom field types (text, number, date, pick-list) map to Acumatica's PXString, PXDecimal, PXDateTime, and PXStringList data types respectively.

Daftra file attachments on clients, invoices, and products re-upload to Acumatica's NoteDoc table linked to the target entity's NoteID. Files are stored in the Acumatica file repository. Large file attachments (>25MB) may require chunked upload. Inline images in Daftra notes are extracted and rehosted as Note attachments with the same entity reference.

Daftra workflow definitions do not have a direct Acumatica equivalent. We export Daftra workflow rules (trigger conditions, assignee routing, field-update logic) as a structured JSON reference document. Your Acumatica admin uses this to rebuild automation rules in Acumatica's Screen automation (SOOrder entry, APInvoice entry) or via Business Events with action handlers. Workflow rebuild is out of scope for data migration pricing.