Migrate from Combit CRM to HubSpot

Combit CRM contacts map 1:1 to HubSpot contacts. All standard properties (name, email, phone, job title) pass through as HubSpot native fields. Contacts without a primary company land as standalone HubSpot contacts and can be associated later via HubSpot's association tool.

Combit CRM companies map directly to HubSpot companies. Company name, domain/website, industry, employee count, and annual revenue translate to HubSpot's equivalent fields. Parent-company hierarchies in Combit CRM surface as a custom Company_Parent_ID__c field on the HubSpot company for manual reconstruction.

Combit CRM deals migrate as HubSpot deals. Deal name, amount, close date, owner, and stage name pass through directly. Combit's free-text deal stage names are mapped to HubSpot pipeline stage values using a value-mapping table built during discovery. Each workflow process in Combit CRM generates its own value-mapping table, ensuring stage labels translate accurately across all deal workflows present in the source system.

Combit CRM workflow processes define a named sales process with ordered steps. Each workflow process maps to a named HubSpot deal pipeline. The pipeline's ordered steps map to HubSpot pipeline stages in sequence, preserving stage order and forecast category settings per stage.

Combit CRM deal stages are free-text strings per workflow process. Each stage name maps to a HubSpot pipeline stage value. Where Combit stages have no exact HubSpot equivalent, the closest stage name is chosen and a stage-rebuild note is generated for the HubSpot admin.

Combit CRM appointments map to HubSpot Meetings (stored as Events). Original start time, end time, location, and linked contact/company associations migrate. Combit appointment status (free/busy/pending) is preserved as a custom HubSpot property Appointment_Status__c because HubSpot Meetings lack a native status flag.

Combit CRM tasks migrate as HubSpot tasks. Subject, due date, completion flag, owner, and linked record associations pass through. Completed task status maps to HubSpot's task completion field. If Combit tasks include priority levels, those map to HubSpot task priority values. Any task notes or descriptions attach to the HubSpot task body field. Recurring task patterns in Combit CRM are noted in the migration plan as HubSpot does not support native recurring tasks without third-party integration.

Combit CRM notes map to HubSpot notes. Note body text and associated contact/company/deal links migrate. Notes attached to multiple records are duplicated as separate HubSpot notes — each linked to one HubSpot record — to preserve the full association context.

Combit CRM file attachments are downloaded from the source system and re-uploaded to HubSpot's file storage. Files are linked to their parent contact, company, or deal record. Files larger than HubSpot's 25MB limit per file are flagged for manual handling before the migration runs.

Combit CRM user records are matched to HubSpot users by email address. Unmatched owners are flagged in the migration plan — your team either creates HubSpot user accounts first or assigns those records to a designated fallback owner. No record lands in HubSpot without a resolved owner.

Combit CRM's daily work processes and process steps define module-level workflow logic that has no HubSpot equivalent. HubSpot workflows are action-trigger-based and cannot import Combit's declarative process maps. We export the full process definition as a structured JSON document so your HubSpot admin can rebuild the logic in HubSpot's workflow editor.

Combit CRM custom properties defined per module map to HubSpot custom properties. Text, number, date, and pick-list types translate directly. Multi-select pick-lists in Combit CRM become HubSpot text properties holding comma-separated values unless your team requests a separate custom object. All custom property names and types are documented in the migration field map before data moves.

Combit CRM call logs, logged emails, and meeting records link to the contact timeline in HubSpot as engagement events. Original timestamp, owner, and subject line are preserved. Email body content migrates as a note attached to the contact when the body is non-empty; otherwise only the engagement record is created.