Migrate from CRM Service to HubSpot

CRM Service contacts map directly to HubSpot contacts. HubSpot's contact model supports email, phone, job title, address, and lifecycle_stage as native properties. Contacts without a primary company in CRM Service land in HubSpot as standalone contacts and can be associated to companies via the Companies object post-migration.

CRM Service company records map to HubSpot companies. HubSpot's Company object includes name, domain, industry, employee count, annual revenue, phone, and address properties. Parent-child company hierarchies in CRM Service map to HubSpot's parent company association on the Company record, preserving corporate structure relationships across the migration.

CRM Service deals map to HubSpot deals. Each deal in CRM Service is associated with a primary company and optionally a contact. HubSpot deals carry amount, close date, pipeline, deal stage, and owner. Stage names are mapped value-by-value from CRM Service to the corresponding HubSpot pipeline stage.

CRM Service deal stages map to HubSpot pipeline stages using value mapping. Each CRM Service stage is matched to a HubSpot stage by name or semantic equivalent. If CRM Service has stages that have no HubSpot equivalent, your admin chooses a fallback stage and the original stage label is preserved in a custom property.

CRM Service tickets or cases map to HubSpot tickets. HubSpot's Ticket object has status, priority, pipeline, resolution SLA, and source channel properties. If CRM Service ticket data includes fields not present in HubSpot's standard ticket schema, those migrate as custom properties on the ticket record.

CRM Service tasks and activities (calls logged, emails sent, notes) map to HubSpot engagements. HubSpot engagements preserve the original timestamp, owner, and association to the contact or company record. The engagement type (call, email, meeting, note) is stored in the engagement type property.

CRM Service owner records are resolved to HubSpot users by email match. If a CRM Service owner email matches a HubSpot user email, the ownerId maps directly. Unmatched owners are flagged as a pre-migration step — your team either creates HubSpot users or assigns records to a fallback owner before the migration runs.

CRM Service custom fields that do not have a HubSpot native equivalent are created as HubSpot custom properties. Your admin reviews the property list before migration to rename, merge, or discard source custom fields. Custom properties are created in HubSpot's property settings and then populated during the migration run.

CRM Service file attachments associated with contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files. HubSpot Files are associated to records via the file upload API. File size limits from the source platform are respected; files exceeding HubSpot's limit are flagged for manual handling.

CRM Service leads or prospects without a closed-won deal are migrated as HubSpot contacts. HubSpot's lifecycle_stage property reflects the lead status: 'Lead' for unqualified prospects and 'Customer' for those with associated closed-won deals. The original source system status is preserved in a custom property for reporting continuity.

CRM Service contact-to-company association labels (if present) map to HubSpot's association labels. HubSpot supports association labels on the Contact-to-Company relationship such as 'Business', 'Partner', or 'Press'. Labels that cannot be mapped are preserved as a custom contact property for reference.

CRM Service campaign membership or static lists have no direct HubSpot equivalent at the CRM level. CRM Service list membership is preserved as a custom contact property (e.g., List_Name__c) so lists can be rebuilt as HubSpot static lists post-migration. Dynamic lists require rebuild using HubSpot's list filters.