Migrate your Priority ERP data

Priority stores Customers as header records with associated price lists, credit limits, and multi-address hierarchies. We map these into the destination's account/contact model, flattening address books and preserving credit terms as custom fields where the target schema does not support them natively.

Vendors share a similar structure to Customers in Priority, with pay-to and ship-from address hierarchies and purchasing-specific fields. We extract the full vendor record including purchasing terms and map them into the destination's vendor/supplier object, renaming fields to match the target's conventions.

Items in Priority carry rich attributes including part numbers, BOM links, stocking dimensions, and warehouse-specific quantities. We extract item headers and their variant attributes, handling multi-warehouse quantity records as child rows. BOM structures are mapped as parent-child relationships in the destination.

Sales Orders include header fields (customer reference, terms, freight) and multi-line details with pricing, discounts, and tax allocation. We extract the full order structure and map line-level data to the destination's order or opportunity product model, preserving order status and dates.

Purchase Orders follow a mirror structure to Sales Orders but belong to the Vendors dimension. We extract PO headers and lines, mapping them to the destination's purchase order or bill model, with attention to received-versus-invoiced quantities for partial fulfillment.

Priority supports multi-segment account codes and complex hierarchies for cost centers and departments. We extract the full account tree and validate segment structure against the destination's account model, flagging any multi-segment accounts that require decomposition or custom field augmentation in the target.

Outstanding invoices and credit memos are tracked as open documents linked to Customers, Vendors, and GL accounts. We extract open document totals, due dates, and aging buckets, then map them as open receivables or payables in the destination, preserving balance-carry-forward semantics.

Projects in Priority track budgets, assignments, billing records, and milestones. We extract project headers and associated WBS rows, time entries, and billing details, mapping them to the destination's project or engagement model and preserving custom fields.

Employee records include compensation history, org unit assignments, and role-based permissions. We extract the employee file noting that salary and benefits data require explicit customer sign-off due to sensitivity, and we map org structure to the destination's department/employee model.

Journal Entries consist of debit and credit lines linked to account codes, with support for reversing entries and recurring templates. We extract full entry details including posting date, period, and source reference, mapping to the destination's journal entry model with attention to reversal flags.

Priority's form generator and workflow builder create business logic embedded in the UI layer that does not export via API. We document the existence of custom forms and workflows during scoping but do not migrate them — customers must rebuild equivalent logic in the target platform post-migration.

Documents attached to Customers, Orders, and Projects are stored as file references in Priority. We export attachments to a file store and create link records in the destination, preserving the association to the parent object. Binary document content is transferred as-is without format transformation.