Migrate from aACE to HubSpot

aACE Organizations map directly to HubSpot Companies. Organization name, industry, phone, website, and address fields carry over as Company properties. Parent-child organization hierarchy in aACE maps to HubSpot's parent Company field. Multi-location organizations may require HubSpot location fields or custom properties for each branch.

aACE Contacts map 1:1 to HubSpot Contacts. Name, email, phone, job title, and address fields align directly. Primary Organization association resolves to HubSpot's primary Company association. Additional organization links in aACE (N:N relationships) map to HubSpot's secondary company associations if available or remain as custom properties.

aACE Projects are the primary revenue-tracking object and map to HubSpot Deals. Project name becomes Deal name, projected amount maps to Deal amount, and project status maps to a HubSpot deal pipeline stage. Multiple aACE project types may map to separate HubSpot pipelines if each type has distinct stage sets. Actual cost and revenue figures migrate as custom number properties on the Deal since HubSpot has no native cost accounting.

aACE Line Items attach to Projects and carry product, quantity, unit price, and discount data. These map to HubSpot Deal Line Items (available in Sales Hub Professional and above). Line item order and association to the target Deal are preserved during migration. Products referenced by line items are created as HubSpot products if they do not already exist.

aACE note records map to HubSpot Notes. Original note body, create date, and associated Contact or Organization are preserved. Rich-text formatting in aACE notes is converted to plain text or HubSpot's note format. Note associations link to the corresponding HubSpot Contact or Company record.

aACE activity records (calls, emails, to-do tasks) map to HubSpot Engagements. Call logs, email subject/body, and task subjects transfer with original timestamps and owner information. Each engagement type (call, email, task) maps to its corresponding HubSpot engagement object, preserving the association to the related Contact or Organization.

Any aACE custom fields defined beyond standard Organization/Contact/Project fields require HubSpot custom properties. FlitStack creates HubSpot custom properties matching the source field type (text, number, date, picklist, checkbox) and maps values during migration. Enterprise tier or a la carte property purchases may be required depending on HubSpot plan.

aACE user accounts are resolved by email address against HubSpot user accounts. Unmatched users are flagged before migration — teams can invite them to HubSpot first or assign their records to a fallback owner. All records migrate with OwnerId populated for audit continuity.

If aACE uses multiple project types with distinct stage sets, each type maps to a separate HubSpot deal pipeline. Stage names are mapped value-by-value from aACE project stages to HubSpot pipeline stages. Stage probability and forecast category are reapplied per pipeline configuration in HubSpot.

aACE file attachments (e.g., project documents, contracts stored on the FileMaker server) are extracted and re-uploaded as HubSpot file attachments on the corresponding Contact, Company, or Deal record. File size limits per HubSpot's storage tier apply — large files may require alternative storage with link-only references.

FileMaker scripts and aACE relationship-triggered automations have no direct equivalent in HubSpot and cannot be exported as portable logic. FlitStack exports aACE automation definitions as documentation so your HubSpot admin can rebuild equivalent workflows in HubSpot's workflow builder. This includes capturing trigger criteria, action sequences, and conditional logic from the source scripts.

aACE invoice, payment, and financial transaction records are accounting ledger entries outside HubSpot's CRM scope. Actual cost, estimated cost, revenue, and billing status fields from Projects migrate as custom number and picklist properties on the Deal. Full accounting records remain in aACE or a dedicated accounting system — they do not migrate into HubSpot.