Migrate from AgileCase to HubSpot

AgileCase contacts map 1:1 to HubSpot contacts. All standard fields (name, email, phone, job title, address) migrate as HubSpot native properties. Owner resolution uses email matching against HubSpot users. Custom fields on the contact object become HubSpot custom properties with type-aware transformation applied for pick-list, numeric, date, and multi-select field types.

AgileCase organizations map to HubSpot companies. Company name, domain, industry, employee count, and annual revenue migrate as HubSpot native company properties. Parent-child company hierarchies map to HubSpot's associated companies model. Industry pick-list values are translated against HubSpot's taxonomy, with unmapped values created as custom pick-list properties.

AgileCase cases representing sales opportunities map to HubSpot deals. Case name becomes deal name, case amount maps to deal amount, and case status maps to deal stage via value mapping against your HubSpot pipeline stages. Case type maps to deal type pick-list (New Business, Existing Business). Case priority migrates as a custom pick-list property on the deal.

AgileCase cases representing support or service requests map to HubSpot tickets. Ticket subject pulls from case name; ticket pipeline stage maps from case status via value mapping. Service hub tier is required for ticket object access in HubSpot. Case priority and type are preserved as custom properties on the migrated ticket.

AgileCase tasks map to HubSpot engagement tasks. Subject, description, due date, assigned user, and completion status migrate with original timestamps preserved. Task associations link to the migrated contact or company record. Unmatched assignees are flagged pre-migration for fallback owner assignment or manual reassignment.

AgileCase documents and attachments migrate as HubSpot Files associated with the parent contact, company, or deal record. File name, content type, upload date, and file size are preserved. Documents associated with multiple cases are linked to the primary case record; secondary associations are logged in a reference property for manual re-linking post-migration.

Every AgileCase custom field on Contact, Company, Case, or Task becomes a HubSpot custom property. Property type is mapped: text to single-line text, number to number, pick-list to dropdown select, date to date picker, and multi-select to multiple checkboxes. We audit custom field count to ensure you remain below HubSpot's 10,000-property limit per object.

AgileCase workflows and automations do not migrate. These must be rebuilt in HubSpot using Automation Hub for operational workflows or Sales Hub sequences for email nurture sequences. We export workflow definitions as a reference document listing trigger events, conditions, and automated actions for your HubSpot admin to use as a rebuild guide.

AgileCase users are resolved by email match against HubSpot users. Unmatched owners — former employees or accounts not yet provisioned in HubSpot — are flagged before migration. Your team either provisions HubSpot accounts for those users or designates a fallback owner before the migration window. No record lands in HubSpot without a valid owner reference.

AgileCase audit trail entries (field changes, status transitions, user actions) are summarized as a custom text property on the migrated record. The summary includes the last modified timestamp, modifying user's name, and significant status transitions. The full audit log is exported as a CSV reference file for compliance or historical review.

AgileCase custom reports cannot migrate to HubSpot. The underlying data migrates so equivalent HubSpot reports can be built, but report definitions, charts, and scheduled exports must be recreated using HubSpot's reporting tools. We provide a data dictionary mapping migrated fields to their HubSpot equivalents for report rebuilding.