Migrate from CRM Runner to HubSpot

CRM Runner contact properties (name, email, phone, address, job title) map directly to HubSpot contact properties. CRM Runner owner email resolves to a HubSpot user by email match; unmatched owners land under a pre-designated fallback owner in HubSpot. All timestamps, including created date and last modified date, are also transferred to maintain historical context.

CRM Runner company name, domain, industry, employee count, and annual revenue fields map to HubSpot company properties. HubSpot's company-domain grouping feature auto-merges contacts by domain post-migration if enabled. Custom company fields such as license numbers or insurance expiry are migrated as HubSpot custom properties, and any missing standard fields are created before data load.

CRM Runner links contacts to their primary company by company name or domain match. HubSpot associates the contact record to the matching company using HubSpot's association API. Contacts without a company link in CRM Runner land as unassociated HubSpot contacts.

CRM Runner job objects translate to HubSpot Deals if the job tracks sales pipeline or revenue. If the job is purely field-service scheduling (technician assignment, GPS location), it becomes a HubSpot custom object (e.g., Service_Job__c) created before migration. The migration plan distinguishes between these two cases before the schema setup phase.

CRM Runner job objects translate to HubSpot Deals if the job tracks sales pipeline or revenue. If the job is purely field-service scheduling (technician assignment, GPS location), it becomes a HubSpot custom object (e.g., Service_Job__c) created before migration. The migration plan distinguishes between these two cases before the schema setup phase. The mapping also preserves job creation and modification timestamps, ensuring a complete audit trail in HubSpot.

CRM Runner job status values (Scheduled, In Progress, Completed, Cancelled) map to HubSpot deal stage pick-list values. Each HubSpot pipeline requires its own stage set; stage probability re-applied based on HubSpot's stage-forecast model. During migration, we also transfer any custom stage labels and ensure that closed-won and closed-lost probabilities align with your sales process.

CRM Runner job owner email resolves to a HubSpot user by email match. If the owner email has no matching HubSpot user, the record lands under the fallback owner; the migration report flags every unmatched owner for manual assignment.

CRM Runner call logs, notes, and email records attached to contacts or jobs migrate as HubSpot engagements. Call type migrates as a HubSpot call engagement with original call date and duration. Notes migrate as HubSpot notes attached to the contact record. Engagement timestamps and owners are preserved.

CRM Runner custom fields on contacts that have no HubSpot standard equivalent become HubSpot custom contact properties (e.g., membership_tier, referral_source). The custom property schema must be created in HubSpot before the migration runs; FlitStack delivers a schema setup plan listing every custom property to create.

CRM Runner custom fields on companies that have no HubSpot standard equivalent become HubSpot custom company properties. Company-level custom fields are typically fewer than contact-level fields but may include industry-specific data (e.g., license_number, insurance_expiry) that requires a custom property in HubSpot.

CRM Runner custom fields on jobs (e.g., job_type, equipment_used, site_address) map to custom properties on the HubSpot Deal record if jobs map to Deals, or on the custom Service_Job__c object if a custom object is used. The migration plan specifies the target before schema setup begins.

CRM Runner bundles VoIP call recording as part of its platform. HubSpot has no native call recording — call recordings must be stored externally (e.g., AWS S3, Google Drive) and re-linked to HubSpot call engagements via a third-party telephony integration (Aircall, JustCall, or HubSpot's built-in calling add-on). FlitStack does not migrate call recording audio files.

CRM Runner captures technician GPS coordinates and site visit history tied to job records. HubSpot has no native GPS or geolocation tracking field. If site visit history is critical for reporting, FlitStack can write location data as a HubSpot custom property or note on the deal record, but real-time GPS tracking requires a field-service app integration post-migration.