Migrate from aACE to Microsoft Dynamics 365 Sales

aACE Accounts (the primary customer and vendor record) map directly to Dynamics 365 Account. The Account holds billing and payment terms, and all linked Orders, Invoices, and Locations reference it. We preserve the aACE Account number as AccountNumber and the primary contact reference as a Lookup to the related Contact record.

aACE supports multiple locations per Account, each with its own address and contact record. We migrate each location as a separate Dynamics 365 Customer Address record linked to the parent Account, using the address purpose (billing, shipping, primary) from aACE's location type field. Primary location address populates the Account's default billing and shipping address fields.

aACE Items (inventory-part records holding SKU, description, unit cost, and pricing tiers) map to Dynamics Product2. The aACE Item number becomes Product Number, and pricing tiers migrate as Price List entries in the Dynamics default price list. If the customer uses aACE's multi-currency pricing, we split Price List Items by currency.

aACE Sales Orders map to Dynamics Opportunity. The aACE order number becomes Opportunity Name, order total maps to Amount, and the Sales Order date maps to Close Date. Order status from aACE (open, closed-won, closed-lost) determines the Dynamics StageName. aACE's linked Line Items migrate as Opportunity Product records.

aACE Order Line Items link to Items and carry quantity and unit price. We map each line to a Dynamics Opportunity Product record, resolving the PricebookEntry reference using the Item's SKU and the active price list. Extended price and discount amounts preserve where aACE tracks them at the line level.

aACE A/R Invoices map to Dynamics Invoice records. Open invoices migrate with full balance remaining and payment history so the A/R team can pursue collections post-migration. Closed invoices migrate as historical records with invoice status set to Paid. We flag open invoices as operationally critical and migrate them in the first batch before any other object.

aACE Purchase Orders link to Vendors, Items, and optionally to the originating Sales Order. Microsoft Dynamics 365 Sales does not include Purchase Order management; it requires Dynamics 365 Finance or Supply Chain Management as a separate license. We do not migrate Purchase Orders as standard scope. We deliver a written inventory of open POs with vendor, line items, and receipt status for the customer's ERP implementation team to handle in a separate engagement.

aACE Projects hold job headers with linked Tasks, Time entries, and billing records. Microsoft Dynamics 365 Sales does not include project management; Project Operations is a separate license. We do not migrate Projects as standard scope. We deliver a written inventory of active Projects with their linked Tasks, estimated hours, and billing status for the customer's Project Operations implementation team.

aACE Tasks link to Projects and optionally to Accounts and Orders. We map task status, assignee, due date, and any custom flag fields to the corresponding Dynamics Task fields. Assignee resolves via the Employee-to-User mapping by email. High-volume task exports from aACE use FileMaker's chunked cache table approach with each batch validated before proceeding.

aACE Employee records (active roster with role and department) map to Dynamics User records. We resolve each Employee by email against the destination Dynamics User table. Historical payroll records and inactive employees are not migrated as Users; they are written to a separate audit table in Dynamics as custom records if the customer requests retention.