Migrate from Capsule CRM to HubSpot

Capsule Party records with type='person' migrate directly to HubSpot Contacts. The contact's email, phone, job title, address fields, and owner assignment map to HubSpot's standard Contact properties. The original Capsule party ID is stored as a custom field for delta-run de-duplication.

Capsule Party records with type='organisation' migrate to HubSpot Companies. Company name, domain, industry, number of employees, and annual revenue map to HubSpot Company properties. Parent-child organization hierarchies in Capsule map to HubSpot's Parent Company field. If multiple parent-child levels exist in Capsule, we preserve the full hierarchy by mapping the top-level organization as the parent in HubSpot.

Capsule Opportunities migrate as HubSpot Deals. Deal name, amount, stage, probability, expected close date, owner, and party association transfer to HubSpot Deal properties. The Capsule opportunity ID is preserved as hs_deal_id on the HubSpot deal for traceability. Lost opportunities in Capsule are migrated with a closed-lost stage value matching your HubSpot pipeline configuration.

Capsule pipeline stage names map to HubSpot deal pipeline stage values. We read Capsule's pipeline configuration via API and create matching pipeline stages in HubSpot. Stage probability percentages from Capsule transfer to the HubSpot stage probability field for forecasting continuity.

Capsule Cases migrate to HubSpot Tickets. Case status (open/closed/pending), priority, owner, subject, and associated party link transfer to HubSpot Ticket properties. HubSpot's ticket status values are mapped from Capsule's case status using value-by-value mapping. Resolved cases in Capsule transfer with their final resolution notes preserved in the ticket description field for support history continuity.

Capsule Tasks migrate to HubSpot Tasks. Task subject, due date, owner, completion status, and associated party or opportunity link transfer to HubSpot. Completed tasks are marked as such in HubSpot. Open tasks without a due date receive the Capsule creation date as a fallback.

Capsule notes migrate as HubSpot engagement notes. The note body text transfers directly. However, Capsule notes exported via CSV lose rich-text formatting (bullets, line breaks); we handle this by normalizing note text and flagging records where formatting loss exceeds a threshold so your team can review before final import.

Capsule tags and categories used for contact classification that don't map to HubSpot's standard properties are migrated as HubSpot custom single-line text or multi-line text properties. Tags are comma-separated in the custom property. Your team decides whether to map tag values to HubSpot's contact property options or store them as reference text.

Capsule custom fields on Party records migrate as HubSpot Contact custom properties. Field type mapping: Capsule text fields become HubSpot single-line text; Capsule list fields become HubSpot enumeration (dropdown) properties with their original options preserved. This requires custom property creation in HubSpot before migration runs.

Capsule custom fields on Opportunity records migrate as HubSpot Deal custom properties. Fields that record deal-specific metadata (contract type, renewal date, product line) are created as HubSpot deal properties with matching types. Value list options are mapped using HubSpot's enumeration field option management.

Capsule owner assignments resolve to HubSpot users by email address lookup. Unmatched owners are flagged before migration — your team either invites them to HubSpot first or reassigns records to an existing HubSpot user. No record lands without a valid HubSpot owner assignment.

Capsule's party-to-opportunity associations migrate to HubSpot's contact-to-deal associations. Each Capsule opportunity-party link creates a corresponding contact-deal association in HubSpot. Multiple contacts linked to one opportunity each get their own association row. If a contact in Capsule is linked to multiple opportunities, each opportunity link becomes a separate deal association in HubSpot maintaining the full relationship graph.

Capsule file attachments on parties, opportunities, and cases are downloaded and re-uploaded to HubSpot Files. Files are associated with the corresponding HubSpot record (contact, company, or deal). HubSpot's 25MB per-file limit is enforced; files exceeding this are flagged for manual handling.

Capsule Workflow Automations and Tracks do not migrate to HubSpot. We export Capsule workflow definitions as a structured reference document listing each automation's trigger condition, action steps, and track milestones. Your HubSpot admin uses this to rebuild automations in HubSpot's workflow builder.

Capsule Projects are project-management records without a direct HubSpot CRM equivalent. We assess each project's purpose: standalone project records migrate as HubSpot custom objects (Enterprise only); project records tied to a sales milestone migrate as deal-associated records. Your team decides the mapping strategy before migration runs.