Migrate from ConnectWise PSA to HubSpot Service Hub

ConnectWise Companies map directly to HubSpot Companies. HubSpot requires a single primary domain per company record; multi-location ConnectWise companies with separate addresses are created as individual HubSpot company records linked by association. Original ConnectWise company ID is preserved as a custom property for delta-run deduplication.

ConnectWise Contacts map directly to HubSpot Contacts. Email, phone, name, and address fields transfer as direct properties with standard field mappings. ConnectWise's primary-contact flag maps to HubSpot's lifecycle_stage (set to 'customer') when the contact is associated with an active agreement. For contacts with multiple roles or relationships in ConnectWise, additional manual review may be needed to ensure accurate lifecycle stage assignment in HubSpot.

Each ConnectWise Service Board becomes a HubSpot Ticket Pipeline. Board-specific SLA rules, queue names, and priority configurations are documented in the migration plan as HubSpot SLA configuration references. Boards without a HubSpot equivalent (e.g., emergency escalation queues) are flagged for manual rebuild in HubSpot workflow automation.

ConnectWise Tickets map to HubSpot Tickets with full property transfer: summary, description, priority, status, assigned technician, created date, updated date. Internal notes on ConnectWise tickets become HubSpot internal ticket notes, preserving the original formatting and author information. Conversation threads transfer as HubSpot ticket communication history, maintaining the chronological order of updates for complete audit trails.

ConnectWise Agreements (recurring service contracts, SLAs, maintenance agreements) have no native HubSpot equivalent. We migrate agreements as a custom object (Agreement__c) with fields for agreement type, start/end dates, scope, and associated company. Rebillable agreement terms are documented for rebuild in HubSpot's Products and Quotes module.

ConnectWise Time Entries track billable and non-billable work against tickets. HubSpot has no native time-tracking object. Time entries are migrated as a custom object (TimeEntry__c) linked to the parent ticket and contact, preserving hours logged, work date, technician name, and billable flag.

ConnectWise Products and Services catalog maps to HubSpot's Product object. Product name, SKU, unit cost, and billing type transfer as HubSpot product properties. Bundled product configurations in ConnectWise are preserved as product bundles in HubSpot's Sales Hub if that module is active.

ConnectWise company-level and board-level custom fields migrate to HubSpot custom properties on the corresponding object (Contact, Company, or Ticket). Note: Custom property creation in HubSpot requires Operations Hub Starter or Professional. We document all custom field types (text, number, picklist, date) for correct HubSpot property type assignment.

ConnectWise Knowledge Base articles migrate to HubSpot Knowledge Base with full fidelity. Article titles, body content, category assignments, and publication status transfer completely. Article-to-ticket associations are preserved as ticket property references in HubSpot for reporting continuity. Attachments embedded within article bodies are exported and reattached to the corresponding HubSpot knowledge base articles during the migration process.

ConnectWise Projects have no direct HubSpot equivalent. Projects are migrated as a custom object (Project__c) with start date, end date, status, budget, and associated company/contact links. Project task details are preserved as a child custom object (ProjectTask__c) for granular history.