Migrate from Getfly CRM to HubSpot

Getfly CRM customer records map directly to HubSpot Contacts. HubSpot's Contact object uses a flat properties bag — firstname, lastname, email, phone, jobtitle, address fields, and any custom properties are stored as key-value pairs. We map every standard Getfly field to its HubSpot equivalent and create HubSpot custom properties for any Getfly CRM fields that have no direct counterpart.

If Getfly CRM records contain a lead-status or lifecycle-state field indicating pre-conversion records, those route to HubSpot's Lead concept. HubSpot differentiates Leads (unqualified prospects) from Contacts (qualified customers) via the lifecycle_stage property — records ending at 'customer' land as Contacts; everything else can optionally split to Lead records based on your HubSpot lifecycle configuration.

Getfly CRM company records map to HubSpot Companies. HubSpot Company properties include name, domain, industry, phone, address, employee count, and annual revenue. Parent-child company hierarchies in Getfly CRM map to HubSpot's Company Associations — the primary company is set as the parent, and child companies are linked via HubSpot's association labels.

Getfly CRM deal records map to HubSpot Deals. HubSpot Deals carry name, amount, close date, pipeline, deal stage, owner, and associated contacts. Each Getfly CRM deal stage maps to a HubSpot Deal pipeline stage by value mapping — stage names, probabilities, and forecast categories are applied per stage from the Getfly CRM source. Deal-to-contact associations use HubSpot's association API to link the Deal to its primary Contact.

Getfly CRM's internal pipeline or stage configuration becomes a HubSpot Deal Pipeline. We create the pipeline in HubSpot, define the stages to match Getfly CRM's stage names and order, and set stage-level probability and forecast category. If Getfly CRM uses multiple independent pipelines, we create a corresponding number of HubSpot Deal pipelines and map deals to their correct pipeline during migration.

Getfly CRM product records (with name, SKU, price, description, images, and custom fields) map to HubSpot Products. HubSpot Products are used in the Deals module — when a Deal references a product, the line-item detail can be captured in HubSpot's product associations. Custom fields on Getfly CRM products migrate as HubSpot custom properties on the Product object.

Getfly CRM tasks — whether classified as calls, emails, or meetings — migrate as HubSpot Engagements. HubSpot's engagement timeline tracks calls, emails, meetings, and notes with original timestamps, owners, and parent-record links. The engagement type (call, email, meeting) is set as a property on the HubSpot engagement record. Notes and internal comments migrate as HubSpot Notes attached to the parent Contact or Company record.

Getfly CRM marketing campaigns and campaign memberships have no direct HubSpot equivalent in the CRM alone. Marketing campaign data is preserved as a custom field on the associated Contact records (campaign_source, campaign_date) for reference. Full campaign logic and UTM attribution are rebuilt in HubSpot's Marketing Hub with the exported campaign names as a rebuild guide.

Getfly CRM's integrated PABX/VoIP call center generates call records with duration, direction (inbound/outbound), recording links, and agent assignment. These migrate to HubSpot Call Engagements with the call direction, duration, and timestamp preserved as engagement properties. Call recordings require a destination storage solution — we re-upload to HubSpot Files and associate with the relevant Contact record.

Getfly CRM custom objects map 1:1 to HubSpot Custom Objects. HubSpot Custom Objects (available on Enterprise-tier hubs) require pre-creation in HubSpot settings before migration — we deliver a schema plan specifying the object name, display label, primary property, and association labels needed. N:N relationships between custom objects use HubSpot's unlabeled associations API.

Getfly CRM KPI measurement records (performance scores, targets, achievement metrics per user or deal) have no native HubSpot equivalent. We migrate the most recent KPI snapshot as custom properties on the Contact or Deal record — your team defines the reporting logic in HubSpot using those fields as source data for custom reports.

File attachments on Getfly CRM customer records, deal records, and tasks are downloaded and re-uploaded to HubSpot Files. Files are associated with their parent record (Contact, Company, Deal) using HubSpot's file association API. File size limits for HubSpot Files apply — files over the HubSpot size threshold are flagged and redirected to your connected Google Drive or OneDrive integration.