Migrate your aACE data

Accounts is the primary customer/vendor record in aACE, holding billing and payment terms. All linked Orders, Invoices, and Purchase Orders reference the Account. We map Accounts 1:1 and preserve the address and payment-term fields.

Items are the inventory-part records holding SKU, description, unit cost, and pricing. They link to Sales Orders, Purchase Orders, and Invoices as line items. We preserve Item costs, pricing tiers, and inventory quantities at migration date.

Sales Orders are the transactional core of aACE, linking a Customer Account to Line Items and spawning Invoices and Purchase Orders. We map all open orders with their line items and related Purchase Orders in sequence.

aACE tracks both open A/R and historical closed Invoices. Open invoices migrate with full balance and payment history so the A/R team can pursue collections. We flag closed invoices separately for optional historical migration.

Purchase Orders in aACE link to Items, Vendors, and the originating Sales Order where applicable. We map PO headers, line items, and received quantities. Partial receipts are preserved as-is at migration date.

Projects in aACE hold the job header and link to Tasks, Time entries, and billing records. We map Project status, assigned Users, and all related child records. Archived or completed Projects are migrated on a period-by-period basis.

Tasks are the unit-of-work records linked to Projects and optionally to Accounts and Orders. We preserve task status, assignee, due date, and any custom flag fields. High-volume task exports use the FileMaker cache-table batch approach.

Employee records hold compensation, department assignment, and timekeeping data. We map the current active employee roster with role and department. Historical payroll records are migrated as separate line-item batches by effective period.

aACE allows custom fields on most standard objects via FileMaker. Custom field names, types, and picklist values vary by tenant. We discover custom field definitions during the scoping phase and build a per-field mapping table before writing to the destination.

Distribution Lists are referenced in the aACE export documentation as address-book groupings. These are FileMaker portal-based records and migrate as a many-to-many join table with contact references.

aACE stores document links and attachments within FileMaker containers. We do not migrate binary container data via export scripts. Customers with attachment requirements are directed to a separate document-migration step using FileMaker's native export.

Multiple locations per Account are supported in aACE. Each location carries its own address and contact record and links to related Orders and Purchase Orders. We map all location records and preserve the primary-location flag.