Migrate from CallPro CRM to HubSpot

CallPro contact records map directly to HubSpot Contacts. Every standard field — name, email, phone, address, job title — maps to HubSpot's equivalent contact property. CallPro owner ID resolves by email match against HubSpot users. Contacts without an email are flagged for manual review before import.

CallPro company records map to HubSpot Companies. Standard fields — company name, domain/website, industry, employee count, annual revenue, phone, and address — translate directly to HubSpot’s equivalent company properties. CallPro’s parent‑company hierarchy is preserved via HubSpot’s parent company association using the parent company ID field; any missing parent references are flagged for resolution. Custom company fields become HubSpot custom properties, preserving pick‑list values and data types.

CallPro campaign membership does not have a direct HubSpot equivalent. We create a custom multi-checkbox property on HubSpot Contacts (Campaign_Membership__c) and populate it with CallPro campaign names. For complex campaign hierarchies, a HubSpot custom object is created to preserve campaign-level data independently.

CallPro sales orders map to HubSpot Deals. Deal name, amount, close date, and owner map to HubSpot Deal properties. CallPro deal status values map to HubSpot pipeline stage values via value-by-value mapping per pipeline. Each CallPro pipeline maps to one HubSpot Deal pipeline.

CallPro's sales-order status labels map to HubSpot Deal pipeline stages. HubSpot allows multiple pipelines with distinct stage sets — we create a HubSpot pipeline for each CallPro pipeline and map stage names value-by-value. Stage probabilities are set per HubSpot pipeline configuration.

CallPro call logs migrate to HubSpot's Calls object. Each call record captures direction (inbound/outbound), duration, disposition, outcome, and original CallPro timestamp. Calls are linked to the HubSpot Contact by email match. Owner is resolved by email match to HubSpot user.

CallPro email activity linked to contacts migrates to HubSpot Emails, preserving subject, body, timestamp, and owner information. Each email is linked to the corresponding HubSpot Contact by email address match; HTML formatting and plain‑text versions are retained where present. If CallPro tracks thread IDs, those associations are mapped to HubSpot’s email thread property, and any email attachments are stored in HubSpot Files before being linked back to the email record.

CallPro tasks and notes map to HubSpot Tasks and Notes respectively, preserving original create dates, owners, and parent record associations. Task due dates, priority flags, and status values are translated to HubSpot task properties, and any task attachments are stored in HubSpot Files before being linked to the task. CallPro note bodies, including rich‑text formatting, migrate to HubSpot Note body fields, with hyperlinks and images retained where CallPro stores them.

CallPro file attachments on contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files. Files are associated back to the original record in HubSpot. HubSpot's 115 MB file size limit applies — files exceeding this are flagged for splitting.

CallPro custom fields on contact records that have no HubSpot standard equivalent become HubSpot custom contact properties. Field type is preserved — pick-list values map value-by-value, text fields become text properties, number fields become number properties. Custom property names in HubSpot use the internal label format.

CallPro custom company fields migrate to HubSpot company custom properties. Industry-specific pick-list values require value-by-value mapping where CallPro's options differ from HubSpot's standard industry pick-list. The mapping plan flags any pick-list values with no HubSpot match for admin decision. All other field types such as text, number, date, and checkbox fields are mapped to HubSpot equivalents, preserving data integrity.

CallPro lead records without an associated deal route to HubSpot Contacts with lifecycle_stage set to 'lead'. CallPro leads with active sales orders route to HubSpot Contacts with lifecycle_stage set to 'customer'. Lifecycle routing is applied based on CallPro's lead status and deal association fields.