Migrate from Copyl to Acumatica

Copyl customers map to Acumatica ARCustomer records. Acumatica requires CustomerCD (display ID) and Name; Copyl customer names and IDs populate those fields. Primary contact and address details map to the related Contact and Address sub-tables. We create the Customer record first so AR invoices can reference it via CustomerID.

Copyl vendors map to Acumatica APVendor records. Acumatica requires VendorCD and VendorName; we map Copyl vendor name to VendorName and any Copyl vendor code to VendorCD. Terms, credit limit, and remittance address map to the corresponding Acumatica vendor sub-tables. Vendor records must exist before AP invoices or purchase orders can be created.

Copyl products map to Acumatica InventoryItem DAC with ItemClass defining the item type (Stock, Non-Stock, or Service). Copyl unit-of-measure and cost prices map to the Price/Cost schema on InventoryItem. If Copyl tracks lot or serial numbers, we map those to InventoryItem's lot/serial classes in Acumatica's warehouse management.

Copyl chart-of-accounts entries map to GLAccount DAC records. Acumatica requires AccountCD (the account code) and Description; we map Copyl account codes and descriptions directly. Active/inactive status from Copyl maps to the Active flag on GLAccount. Subaccounts (Acumatica's dimension breakdown) may require custom fields or segment mapping depending on Copyl's account structure.

Copyl sales documents map to SOOrder and its associated SOLine records. Acumatica requires a valid CustomerID reference, so we run the Customer migration step first. Copyl document dates map to SOOrder.OrderDate, totals map to SOOrder.LineTotal, and order statuses map to Acumatica's open/halted/completed statuses. Historical closed orders migrate as completed records with their original close dates.

Copyl purchase records map to APInvoice for bills or APBill for formal AP documents. Vendor reference is mandatory, so the Vendor step runs first. Copyl invoice amounts and dates map to APInvoice.DocDate and DocBal, with line items populating APTran detail records. Prepaid or credit memos map to the corresponding AP document types in Acumatica.

Copyl project or engagement records do not have a direct Acumatica equivalent until PMProject is enabled. We create a PMProject record for each Copyl project, with project code, name, status, and budget fields mapped. If Copyl stores task-level breakdowns, those map to PMTask sub-records under each project. This requires the Project Accounting module to be active in the Acumatica license.

Copyl's custom entity types map to either existing Acumatica DACs extended with Usr-prefixed custom fields, or to new custom DACs created in the Acumatica Customization Project. We audit Copyl custom entity schemas during the data assessment, then generate Acumatica field definitions and create them before the migration run. N:N relationships between custom entities map to Acumatica's custom DAC with junction table design.

Copyl contacts map to the Contact DAC in Acumatica. We link contacts to their parent Customer or Vendor record via the CustomerID or VendorID reference. Email, phone, job title, and address fields map directly to their Acumatica counterparts. If Copyl stores contact-specific notes or custom properties, those migrate to Contact's extension fields (Usr-prefixed) or related Note DAC records.

Copyl file attachments and document references map to Acumatica's Note DAC attached to the relevant parent record, or to Files for binary attachments. We re-upload Copyl files to Acumatica's file storage and attach them to the corresponding Customer, Vendor, SOOrder, or PMProject record. File size limits follow Acumatica's attachment constraints per document type.

Copyl workflow definitions, approval chains, and automation rules have no Acumatica equivalent and do not migrate. We export Copyl workflow definitions as a structured reference document that your Acumatica consultant uses to rebuild equivalent automation in Acumatica's Screen-based or Visual Branch workflows. This is disclosed upfront so the rebuild effort is scoped before migration begins.

Copyl report and dashboard configurations are destination-platform-specific and do not transfer. The underlying data — transactions, balances, history — migrates to Acumatica and is queryable through Acumatica's Report Designer and Generic Inquiries. We flag Copyl report field names so your Acumatica report writer can reconstruct equivalent outputs with the migrated data.