Migrate from Nimble CRM to HubSpot

Nimble contacts map directly to HubSpot contacts. HubSpot stores contact properties in a flat properties bag (properties.firstname, properties.email). We map every Nimble standard field to its HubSpot equivalent property name. Nimble contacts without a company association land in HubSpot as contacts with no primary company.

Nimble does not separate leads from contacts — all contacts live in one object. HubSpot uses lifecycle_stage to distinguish early-stage contacts from customers. We preserve the full Nimble contact record in HubSpot contacts and populate lifecycle_stage based on the contact's group or tag membership, defaulting to 'lead' where no segment signal exists.

Nimble companies map 1:1 to HubSpot companies. Company properties (name, domain, industry, phone, address) map to HubSpot company properties with identical names or close equivalents. Nimble parent-child company hierarchies map to HubSpot's parent company lookup. Nimble's custom company fields, such as industry classification or employee count, map to HubSpot company properties with matching names. If Nimble uses pick-list fields, the values are created as HubSpot pick-list options during property setup.

Nimble allows each contact to be associated with multiple companies simultaneously. HubSpot contacts have one primary company (via the hubspot_owner_id or company association field) plus optional secondary associations. We migrate the most recently modified company as primary and surface the rest as secondary HubSpot contact-company relationships.

Nimble deals map directly to HubSpot deals. Each Nimble deal retains its name, amount, stage, close date, and owner. Nimble's single-pipeline or multi-pipeline configuration maps to HubSpot deal pipelines — each Nimble pipeline becomes a HubSpot pipeline with its own stage labels and probability weights.

Nimble deal stages map to HubSpot deal stages by value. Each Nimble pipeline maps to a corresponding HubSpot pipeline, and the stage names within each pipeline map one-by-one. Stage probability values are reapplied based on HubSpot's stage configuration. Closed-won and closed-lost statuses align across platforms.

Nimble logged calls migrate to HubSpot engagements with type=Call. The call subject, body, duration, direction (inbound/outbound), and timestamp are preserved. Call owner resolves by email match to HubSpot user. Call is linked to the associated contact via HubSpot's engagement association.

Nimble logged emails migrate to HubSpot engagements with type=Email. The email subject, body, timestamp, and associated contacts are preserved. HubSpot creates engagement records linked to the contact. Note that email content and attachments may be subject to HubSpot's file size limits.

Nimble calendar events migrate to HubSpot engagements with type=Meeting. Title, body, start time, end time, location, and associated contacts are preserved. Owner resolves by email match to HubSpot user. HubSpot displays meetings on the contact's timeline under the Engagements section.

Nimble notes map to HubSpot notes. The note body, create date, and associated contacts or companies are preserved. HubSpot notes display on the contact timeline and company timeline. If the Nimble note contains rich text, formatting is simplified to plain text or basic HTML consistent with HubSpot's note rendering.

Nimble custom data fields on contacts, companies, and deals require HubSpot custom properties. We create HubSpot custom properties (type matches Nimble field type — text, number, date, dropdown) before import and map the data during migration. Custom property names are normalized to HubSpot's lowercase-with-hyphens naming convention.

Nimble tags do not have a direct HubSpot equivalent. Tags are migrated as HubSpot static list memberships — contacts with tag 'referral-partner' are added to the 'referral-partner' list. For Nimble tags that represent behavioral data, we recommend recreating equivalent HubSpot lists and populating them with HubSpot workflows post-migration.

Nimble groups and smart lists segment contacts by criteria. HubSpot lists serve a similar segmentation role. We map Nimble group names to HubSpot list names and add matching contacts. For Nimble smart lists with dynamic membership rules, we document the logic for manual recreation as HubSpot lists with filter conditions.

Nimble owner records map to HubSpot users. Resolution happens by matching the Nimble owner email address against HubSpot user email addresses. Unmatched owners are flagged before migration — your team either invites them to HubSpot or reassigns their records to an existing HubSpot user before the migration runs.

Nimble enriches contact records with social profile data (LinkedIn, Twitter, Facebook URLs) automatically. This enriched social data is stored in Nimble's profile cache and is not exportable as part of a standard CSV export. We preserve the social profile URLs as HubSpot custom properties if they appear in the export — otherwise the social enrichment is not migrated and must be refreshed using HubSpot's enrichment tools post-migration.

Nimble workflows (the Workflow tab with kanban-style process boards) do not migrate to HubSpot. HubSpot's workflow engine uses different trigger types, conditions, and actions. We export your Nimble workflow definitions as a reference document for your HubSpot admin to rebuild using HubSpot's workflow builder. Priority goes to workflows that affect deal stage progression and follow-up task creation.

Nimble email templates and sequence templates do not migrate to HubSpot. HubSpot has its own template library with CRM-specific merge tags. We export your Nimble template content as a text reference document so your team can recreate them in HubSpot's template editor.

File attachments on Nimble contacts, companies, and deals are re-uploaded to HubSpot Files and associated with the target record. HubSpot's file size limit applies (default 25 MB per file). Files exceeding this limit are flagged for manual handling. We preserve the original filename and attach the file to the corresponding HubSpot record on migration.

Nimble deal-contact associations map to HubSpot deal-contact associations. A Nimble deal linked to three contacts creates a HubSpot deal with the same three contacts associated via HubSpot's deal-contact association model. Association order is preserved where Nimble provides it. If a deal has no associated contacts in Nimble, the deal will be imported as a standalone HubSpot deal, and you can manually link contacts afterward.

The original Nimble record ID is stored as a HubSpot custom property (nimble_record_id) on each record for traceability, delta-run de-duplication, and rollback identification. This property is invisible to end users but critical for migration audit and future sync operations. This ID property is indexed for fast lookups and can be used in HubSpot workflows to reference the original Nimble record.