Migrate from Agile CRM to HubSpot Service Hub

Agile CRM Contacts map directly to HubSpot Contacts. Every contact's email address is the dedupe key. We preserve Agile CRM custom fields (type=CUSTOM in the REST API) as HubSpot custom properties created in the portal's property settings before import. Lead score, tags (from Labels), and contact owner all migrate. The Agile CRM contact-company link migrates as a HubSpot Company association resolved at import time.

Agile CRM Companies (Accounts) map to HubSpot Companies. Company domain, industry, phone, address, and website migrate. Agile CRM enforces a single Company per Contact — we validate this constraint during the pre-migration audit and flag any contacts with multiple companies so the customer decides which association to preserve. HubSpot Company is created before Contact import so the association lookup resolves at insert time.

Agile CRM Helpdesk Cases map to HubSpot Tickets. The Case subject becomes Ticket subject, case description becomes Ticket description, and case status (Open, Pending, Resolved, Closed) maps to HubSpot Ticket pipeline stages that we configure before migration. Agile CRM Groups map to HubSpot Teams and become the Ticket owner team. Canned Responses do not migrate via API — we document each active canned response with its body text for manual rebuild in HubSpot. Labels migrate as Ticket Tags.

Agile CRM case conversation threads (agent replies and customer messages) migrate as HubSpot Engagements of type note attached to the Ticket object. Each message preserves its timestamp, author, and body text. The original message direction (inbound/outbound) migrates as a custom property so the agent can distinguish customer replies from outgoing responses without reconstructing the thread manually.

Agile CRM Deals map to HubSpot Deals. Deal name, value, stage, owner, expected close date, and associated Contact and Company migrate. Custom Deal Milestones map to HubSpot Deal stage names. Agile CRM's Custom Deal Tracks (multi-lane pipeline) map to multiple HubSpot Deal pipelines if the customer uses them — each pipeline is a separate HubSpot Deal pipeline we configure before migration.

Agile CRM Tasks (unlimited on all paid tiers) map to HubSpot Tasks with title, body, due date, priority, status, and owner preserved. Linked-entity relationships (task to contact, company, deal) migrate as HubSpot associations resolved at import time via the associations API. Completed-at timestamp migrates as the Task completion date.

Agile CRM call engagements (logged under the Contact timeline) map to HubSpot Engagements of type call. Call duration, disposition, direction, and recording URL (if stored in Agile CRM) migrate as call-specific properties on the HubSpot engagement. The call attaches to the original Contact record via the HubSpot engagements API.

Agile CRM email engagements map to HubSpot Email engagements. Subject, body, direction, and timestamp migrate. Emails attach to the Contact record and optionally to the associated Company and Deal via HubSpot's associations API. Attachments referenced in email bodies migrate as file attachments linked to the engagement.

Agile CRM meeting engagements map to HubSpot Meeting engagements. Title, date, time, location, and attendee list migrate. Attendees resolve to HubSpot Contacts by email match and associate to the meeting engagement.

Agile CRM note engagements map to HubSpot Note engagements attached to the Contact record. Note body migrates as plain text. If the Agile CRM note contains inline images, we export them as file attachments and link them to the HubSpot note.

Agile CRM Groups (helpdesk queues and team-based access partitions) map to HubSpot Teams. We preserve group membership by mapping each Agile CRM user to their corresponding HubSpot user and assigning them to the correct HubSpot Team. If the destination HubSpot account does not yet have Teams configured, we create them during the schema configuration phase.

Agile CRM Labels (tagging Contacts, Deals, and Cases) map to HubSpot Tags. We preserve per-object associations — a Label applied to both a Contact and a Deal becomes a Tag on both the HubSpot Contact and Deal. Tag names and their per-object usage counts are documented during scoping.

Agile CRM custom fields on Contacts, Companies, Deals, and Cases (exposed as type=CUSTOM in the REST API) migrate to HubSpot custom properties. We discover all custom fields during the export audit, create the corresponding HubSpot properties (with correct types: text, number, date, checkbox, dropdown) before import, and map field values during the data load. Multi-select custom fields in Agile CRM map to HubSpot multi-checkbox or multi-select properties.