Migrate from Exxas Cloud Business Platform to Acumatica

Exxas stores customers and contacts within its unified CRM area. Acumatica separates customers (AR.Customer) from contact people (Contact DAC). We split Exxas contacts into customer records with primary contact persons linked via ContactAccountLink. Email addresses and phone numbers map directly; Exxas custom data masks on contacts translate to Acumatica UDFs on the Contact DAC.

Exxas companies map to Acumatica customers (B2B) or vendors (B2B supply side). The company name, domain, industry, and address fields map directly to the corresponding AR.Customer fields. Exxas parent-child company hierarchies map to Acumatica's parent customer structure. Tax ID, annual revenue, and number of employees fields also map to AR.Customer. If multiple locations exist, each address maps to a separate Address DAC entry.

Exxas deals with pipeline stages map to Acumatica CRM Opportunities. Exxas deal amounts, probabilities, and close dates map to Opportunity.Amount, Opportunity.Probability, and Opportunity.CloseDate. Exxas pipeline-to-stage routing requires value-by-value mapping since the two platforms define pick-list values independently. Deal owner information maps to Opportunity.OwnerID, and any Exxas custom fields on deals become UDFs on the CR.Opportunity DAC.

Exxas project records map directly to Acumatica PM.Project. Project name, description, status, start and end dates, budget amounts, and owner assignments transfer as-is. Exxas task-line items within projects map to Acumatica project tasks (PM.Task DAC). Time entries against projects translate to Acumatica TimeEntries linked to the project.

Exxas products with stock tracking map to Acumatica InventoryItem DAC. Products defined as services or non-inventory items in Exxas map to Non-Stock Items (INNonStockItem DAC). Exxas pricing tiers, cost prices, and margin settings require value mapping to Acumatica price classes and customer price classes.

Exxas service tickets map to Acumatica CRM Cases. Subject, description, priority, status, assignee, and resolution notes transfer directly. Exxas SLA configuration on tickets maps to Acumatica case SLA definitions, though SLA rules require reconfiguration in Acumatica Case Management settings. Any Exxas custom fields on tickets become UDFs on the CR.Case DAC, and file attachments transfer to the UploadFile DAC linked to each case.

Exxas employee records map to Acumatica EP.Employee. Full name, email, department, job title, employment status, and hire date transfer directly. Exxas absence and time-tracking records translate to Acumatica TimeOff and TimeEntry DACs. Employee manager relationships map to the SupervisorID field on EP.Employee, and any Exxas custom fields on employees become UDFs on the EP.Employee DAC.

Exxas invoices map to Acumatica AR Invoices. Line items, quantities, unit prices, tax amounts, and customer references transfer. Exxas invoice payment status maps to Acumatica AR payment behavior. Historical paid invoices transfer as open documents if you require full transaction history; unpaid invoices transfer as outstanding receivables.

Exxas purchase orders map to Acumatica PO.POOrder. Vendor, line items, quantities, costs, and expected delivery dates transfer directly. Exxas supplier invoices link to the corresponding purchase order on the Acumatica side. Purchase order status values map to PO.POOrder.Status, and any Exxas custom fields on POs become UDFs on the PO.POOrder DAC.

Exxas custom data masks define category-specific fields on contacts, companies, projects, products, or tickets. Each Exxas custom field is evaluated against the target Acumatica DAC and created as a UDF — either as a new database column (UsrFieldName), a name-value CSAnswer pair, or a logical-only field depending on whether the field is used in Acumatica reports or business logic.

Exxas workflows and task packages (automated follow-up sequences within Sales, Service, or Projects) have no Acumatica equivalent. We export workflow definitions as a structured reference document. Rebuilding these automations in Acumatica Automation Tools or third-party integrations is a post-migration step handled by your Acumatica administrator.

Exxas shared mailboxes ([email protected], [email protected]) link incoming email to service tickets. Acumatica does not include a native shared mailbox-to-ticket routing system. Customer email routing must be configured using Acumatica's integration capabilities or a third-party email integration post-migration. Options include the Acumatica Outlook Add-in, Microsoft Power Automate, or a partner email connector; we provide a routing matrix documenting each mailbox and its target case configuration.

Exxas file attachments on records (contacts, projects, tickets) download and re-upload to Acumatica's UploadFile DAC, linked to the corresponding entity record. Large files are subject to Acumatica's storage configuration. File metadata such as name, size, and upload date are preserved, and attachments retain their link to the original record via the NoteID reference in Acumatica.

Exxas general ledger accounts map to GL.Account in Acumatica. Account code, description, type (asset, liability, income, expense), and active status transfer directly. Exxas account hierarchies map to GL.Account parent-child relationships. Subaccount segments map to GL.Subaccount, and tax tags on accounts transfer to the TaxCategory field in Acumatica.