Migrate from aACE to Salesforce Sales Cloud

aACE Accounts are the primary customer and vendor records, holding billing and payment terms. Every Order, Invoice, and Purchase Order references an Account. We map Accounts 1:1 to Salesforce Account, preserving the aACE account type (Customer, Vendor, Both) in a custom picklist field ace_account_type__c and using the Account Name as the dedupe key during import.

aACE supports multiple Company Locations per Account, each with its own address and optional contact. We map each Location to a Salesforce Account Address record (if Location Management is enabled in the destination org) or to a custom address field set on Account if Location Management is not available. The primary location becomes the Account billing address; secondary locations map as additional address records ordered by the aACE location sequence.

aACE Items hold SKU, description, unit cost, and pricing tiers, and link to Sales Orders and Purchase Orders as line items. We map Items to Salesforce Product2 with Standard Price Book entries created during import. The aACE unit cost maps to the Product2 UnitCost field; pricing tiers become custom fields or PricebookEntry tier records depending on the destination org's pricing model.

aACE Sales Orders are the transactional core, linking a Customer Account to Line Items and spawning Invoices and Purchase Orders. We map Sales Orders to Salesforce Opportunity, preserving Order status (Open, Closed Won, Closed Lost) as StageName via a customer-approved stage matrix. The originating Account resolves to the Opportunity AccountId at migration time.

aACE Sales Order Line Items carry Item reference, quantity, unit price, and tax. We map these to Salesforce OpportunityLineItem, resolving Pricebook2Id from the destination org's active Standard Price Book and Product2Id from the Item-to-Product2 mapping. TotalPrice, Quantity, and UnitPrice migrate directly. Tax amounts route to a custom Opportunity field if the destination org tracks tax at the line-item level.

aACE Invoices track both open A/R and historical closed invoices. Salesforce Sales Cloud Invoice is available from Enterprise and Unlimited editions. We map Invoice headers (Invoice Number, Invoice Date, Due Date, Total Amount, Balance) and line items accordingly. If the destination org does not include the Invoice object, we map to a custom Invoice__c object with Invoice Line Items as a related list.

aACE Purchase Orders link to Items, Vendors, and the originating Sales Order. We map PO headers and line items. Partial receipts (items received against a PO that is not yet fully received) preserve their received-quantity state in custom fields on the destination object because standard Salesforce does not include a PO object without Financial Services Cloud.

aACE Projects hold job headers and link to Tasks, Time entries, and billing records. Salesforce does not include a native Project object in standard Sales Cloud. We pre-create a custom Project__c object with fields for Project Name, Status, Start Date, End Date, and Budget, and map Project Tasks to Salesforce Task records with a custom Project lookup field.

aACE Tasks link to Projects and optionally to Accounts and Orders. We preserve Task Subject, Status, Priority, Due Date, Assignee, and any custom flag fields. High-volume task exports run in batches through the FileMaker cache table to avoid memory exhaustion. The assignee resolves via Owner-to-User mapping by email.

aACE Employee records hold name, department, role, and compensation data. We extract the active employee roster with role and department for mapping to Salesforce User records. Employees without a corresponding Salesforce User go to a reconciliation queue for the customer's admin to provision before record import. Historical payroll data migrates as a separate dataset if required.

aACE tenants frequently add custom fields on Accounts, Orders, and Items to support unique distribution and manufacturing workflows. We discover custom field definitions from the customer's FileMaker layout exports during scoping and build the corresponding Salesforce custom fields before migration. Custom fields with no Salesforce equivalent are written as JSON blobs in a legacy_data__c text area field to prevent silent data loss.

aACE Distribution Lists are FileMaker portal-based address-book groupings. These do not have a direct Salesforce equivalent as a list object. We export the list membership (contact reference plus group name) and map it to Salesforce Campaigns with the contacts as CampaignMember records. The customer configures the Campaign type (Newsletter, Event, Promotion) during scoping.