Migrate from aACE to Pipedrive

aACE Accounts are the primary customer and vendor records, holding billing address, payment terms, and credit limits. We map Accounts 1:1 to Pipedrive Organizations, preserving the account name, billing address as the primary address field, and any payment-term custom fields. Multi-location Accounts in aACE create separate Location records that we map as additional Organization address entries in Pipedrive's location model.

aACE stores named contacts as related records linked to an Account, with fields for email, phone, title, and role. We map these to Pipedrive People records with an explicit link to the target Organization via the organization_id field. Contacts without an email address are flagged for manual review before import because Pipedrive uses email as the primary dedupe key.

aACE Sales Orders map to Pipedrive Deals. The Order header fields (order number, total value, status, order date) map to Deal fields (title, value, stage, expected close date). The aACE order status (open, in-progress, closed-won, closed-lost) maps to a Pipedrive pipeline stage that we configure before migration, preserving any custom stage names the customer has defined in aACE.

aACE Sales Order line items (Item SKU, quantity, unit price, extended price) map to Pipedrive Deal Products. We create Product records in Pipedrive during pre-migration, then associate line items to the parent Deal via the Deal-Product linking table. If an aACE Item has no SKU, we generate a slug from the item name and flag it for customer confirmation.

aACE Invoices (open A/R and closed) map to Pipedrive Deals with a closed status. Open invoices migrate with their full balance and due date preserved as custom fields on the Deal so the A/R team retains a record for collections. Historical closed invoices are optionally migrated as completed Deals with a flag indicating they are billing records, not sales pipeline Deals.

aACE Purchase Orders link to Vendors and Items and optionally to a originating Sales Order. Pipedrive has no native Purchase Order object. We create a Pipedrive custom object (purchases_order or similar API name agreed during scoping) with fields for PO number, vendor, line items, received quantity, and status. If the customer does not require PO history, POs are omitted from migration scope.

aACE Projects hold the job header and link to Tasks, Time entries, and billing records. Pipedrive does not have a native Project object. We create a Pipedrive custom object for Projects with fields for project name, status, assigned user, start date, and linked Deal. Tasks within the Project link via a custom Project ID field on the Pipedrive Activity.

aACE Tasks are unit-of-work records linked to Projects, Accounts, and Orders. We map these to Pipedrive Activities (Task type). Task status, assignee, due date, and description migrate directly. The aACE Task link to a parent Project resolves to the Pipedrive Project custom object ID via a lookup table built during pre-migration.

aACE Employee records (name, email, department, role) map to Pipedrive User records. We match by email. Any aACE Employee record without an email address is held in a reconciliation queue. Only active aACE employees with sales or CRM roles are migrated; payroll and compensation fields do not transfer because Pipedrive has no equivalent.

aACE tenants commonly add custom fields to Accounts, Orders, and Items via FileMaker layout tools. We discover these during scoping by reviewing layout screenshots or export templates the customer shares. Each discovered custom field maps to a Pipedrive typed custom field (text, number, date, picklist, or boolean) created before migration. Fields with no Pipedrive equivalent are written as JSON in a note field to prevent silent data loss.

aACE Distribution Lists are FileMaker portal-based groupings of contacts. We export these as a join table linking contact references to list names and recreate them in Pipedrive as Lists with members resolved via the contact email mapping.