Migrate from aACE to Nutshell

aACE Accounts are the primary customer and vendor records holding billing address, shipping address, and payment terms. They map 1:1 to Nutshell Company. Account.Name becomes Company.name, billing address becomes Company address fields, and payment terms are preserved in a custom field payment_terms__c if the customer intends to use Nutshell's billing module. Account is created before any Person import so that the Company lookup is satisfied at Person insert.

Each aACE Account can have multiple Locations, and each Location carries its own address and primary contact. We split each Location into a Nutshell Company record (for multi-location visibility) or into multiple Person records attached to the same Company (for contact-level tracking). The customer chooses the location strategy during scoping. Location address fields map to Person address fields or to additional Company address fields based on the chosen strategy.

aACE Person records linked to an Account map to Nutshell Person records with a Company lookup back to the mapped Account-to-Company record. Person.FirstName, LastName, Email, Phone, and Title migrate directly. The Person's aACE record ID is preserved in a custom field aace_record_id__c for audit.

aACE Sales Orders are the primary sales pipeline records linking a Customer Account to Line Items. They map to Nutshell Deals. The Sales Order number and description become Deal.name, the total order amount becomes Deal.amount, the order status (Open, Closed Won, Closed Lost) maps to a Nutshell pipeline stage, and the expected ship or close date becomes Deal.expected_close_date. Sales Order status is preserved in a custom field sales_order_status__c.

aACE Sales Order Line Items hold Item, Quantity, Unit Price, and Discount. Nutshell has no native line-item object; we map line items into a custom multi-line text field line_items__c formatted as JSON or into individual custom fields (product_name__c, quantity__c, unit_price__c) per the customer's reporting needs. Item SKU migrates to a custom field item_sku__c on the Deal.

aACE Items (SKU, description, unit cost, pricing tier) map to a Nutshell custom Product object we create during schema setup. Item.SKU becomes Product.sku, Item.Name becomes Product.name, and Item.UnitCost becomes a custom field unit_cost__c. If the customer does not require a separate Product catalog, Items are mapped as custom fields on the Deal instead.

Open aACE Invoices (A/R with outstanding balance) are flagged as operationally critical. We map Invoice.Amount, Invoice.Balance, and Invoice.DueDate to Deal-level custom fields invoice_amount__c, invoice_balance__c, and invoice_due_date__c so the A/R team can pursue collections post-migration. Closed historical invoices are archived to a CSV export, not imported into Nutshell's active CRM.

aACE Purchase Orders link Vendors to Items and originating Sales Orders. Nutshell has no native Purchase Order object. Open POs with outstanding receipts are mapped to Nutshell Notes attached to the related Deal or Company for reference. Full PO history is exported as a separate CSV for the customer's accounting records.

aACE Tasks linked to Accounts, Sales Orders, or Projects map to Nutshell Activity records. Task.Subject becomes Activity.name, Task.DueDate becomes Activity.due_date, Task.Status (Not Started, In Progress, Complete) maps to Activity.status, and the assigned User becomes the Activity owner. Tasks without a date are imported as open activities with no due date.

aACE Projects hold job headers with linked Tasks, Time entries, and billing. Nutshell has no native Project object. We map Project.Name and Project.Status to a Deal with custom fields is_project__c = true and project_status__c set. Tasks under the Project link to Deal Activities with a custom project_task__c flag. The customer reviews this mapping during scoping and may choose to archive Projects to CSV instead.

aACE Employee records (name, email, department, role) are used to resolve the Owner mapping for Accounts, Sales Orders, and Tasks. We extract the email-to-name mapping but do not create Nutshell User records from Employees because User provisioning is a separate administrative step. Owners on migrated records are resolved via email lookup against the Nutshell User table.

aACE tenants frequently add custom fields to Accounts, Sales Orders, and Items via FileMaker layouts. There is no metadata API to enumerate them automatically. We request the customer share their FileMaker layout definitions during scoping and build the complete custom field list. Each discovered custom field is created as a typed Nutshell custom field (Text, Number, Date, Dropdown, Checkbox) before migration. Fields that have no Nutshell equivalent are written as JSON blobs in a custom notes field with a warning flag.