Migrate from Pronto Xi to Acumatica

Pronto Customer records map directly to Acumatica Customer entities. The Pronto customer account code becomes the Acumatica Customer ID. Each customer receives its own AR account from the mapped GL account range. Multi-address records require Address table mapping to the Customer's Contact Info section.

Pronto Supplier records translate to Acumatica Supplier entities. The supplier account code becomes the Supplier ID. Each supplier is assigned an AP account from the mapped GL account range. Remit-to addresses and payment terms are carried across as Supplier attributes.

Pronto stock items have a primary UOM and additional UOM rows. Acumatica requires explicit UOM definitions per item with conversion ratios. We translate Pronto UOM rows into Acumatica's INUnit table entries linked to the Stock Item. Lot/serial settings not enforced in Pronto are set to 'no lot/serial' by default unless source data shows tracking.

Pronto PO headers and lines map to Acumatica POHeaders and POLines. The PO status translates through a value map — Released, Pending Approval, Cancelled. Linked supplier and expected receipt warehouse are carried across as foreign key lookups. The mapping also preserves order dates, shipping instructions, and any notes attached to the header or lines, ensuring that historical order context is retained for audit and reporting purposes in Acumatica.

Pronto SO headers and lines map to Acumatica SOOrders and SOLines. Tax zone mapping requires Acumatica's tax zone configuration to be in place before SO lines referencing tax codes are loaded. Open SOs map as Pending Fulfilment; completed SOs are not migrated unless historical reporting requires it.

Pronto multi-level BOMs translate to Acumatica BOM Masters with BOM Lines referencing Stock Items. The bill type (kit, phantom, standard) maps to Acumatica's BOM Type field. Scrap percentages and operation waste ratios are carried as Material Bill line attributes. Additionally, BOM revision histories and effective date ranges are transferred as attributes on the BOM Master record, allowing Acumatica to enforce version control for manufacturing configurations.

Pronto work orders become Acumatica Production Orders. The production order type is set from the source work order category. Material allocations and labour estimates are loaded as production order material and labor lines. The primary routing sequence from Pronto must be manually assigned to Acumatica's Production Order routing steps after migration.

Pronto project or job costing records map to Acumatica PMProjects. Each project is created with the appropriate template. Project attributes including budget, customer link, and cost codes translate across. Where Pronto uses cost codes as separate GL segments, these map to Acumatica's project cost codes.

Pronto GL account codes map to Acumatica Chart of Accounts entries. Account type, posting class, and tax agency flags translate across. Pronto branch or department codes embedded in account segments are stripped and mapped to Acumatica branch-account assignments in the Branch-Account relation screen.

Pronto custom fields require identification, data-type analysis, and Acumatica Customization Project creation. Each Usr field in Pronto is assessed against Acumatica's standard attributes — if no match exists, a Usr-prefixed custom field is added to the relevant DAC extension in the Customization Project editor before data is loaded.

Pronto users are resolved by email match to Acumatica users. Unmatched owners are flagged in the pre-migration report. Their records can be assigned to a fallback owner during migration or the accounts can be provisioned in Acumatica before the migration run.

Pronto document attachments are downloaded and re-uploaded to Acumatica Files. Files are linked to the parent record (Customer, Supplier, SO, PO, Project) using Acumatica's File noteID relation. File size limits are enforced per Acumatica's attachment configuration. During the migration, any file metadata such as creation date, author, and description is preserved and reattached to the corresponding record, maintaining the audit trail for documentation in Acumatica.