Migrate from Nimble CRM to Pipedrive

Nimble Contacts map to Pipedrive People records with a direct field-to-field mapping on standard properties (name, email, phone, address). The OrganizationId on each Person is resolved by matching the Nimble Contact's associated Company name against Pipedrive Organization names during import. Any Contacts without an associated Company are imported as standalone People. Social enrichment fields (LinkedIn URL, Twitter handle, Facebook URL) transfer as text fields on the Person record since Pipedrive has no native social profile lookup.

Nimble Companies map to Pipedrive Organizations. We export Companies first and insert them before any Contact import so that OrganizationId lookups are satisfied at the moment of Person insert. The Organization name is the dedupe key; if a duplicate Organization already exists in Pipedrive, we attach Contacts to the existing record rather than creating a second Organization.

Nimble Deals map to Pipedrive Deals. The Deal title, value, owner, expected close date, and stage label transfer directly. We pre-configure Pipedrive pipeline stages during schema setup to match the stage labels in Nimble. Loss reason and win reason from Nimble custom fields become Pipedrive Deal custom fields. The OrganizationId on each Deal is resolved by matching the associated Company name.

Each Nimble Deal pipeline becomes a Pipedrive Pipeline with corresponding Stages. Stage labels from Nimble are mapped to Pipedrive Stage names, and stage order is preserved. We configure stage probabilities in Pipedrive to match the win likelihood implied by the Nimble stage if those values are available in the export.

Nimble logged calls export via CSV with call duration, timestamp, and disposition. We map these to Pipedrive Activities with type=call. The PersonId is resolved by email match against the migrated People records. Activity timestamps are preserved on the Pipedrive Activity record.

Nimble Events (calendar meetings) map to Pipedrive Activities with type=meeting. Title, start time, end time, location, and attendees transfer. PersonId is resolved by email match. We create a Pipedrive Activity for each Nimble Event found in the export, linking it to the resolved Person record.

Nimble Tasks have no API export path and must come through the CSV export at the 500-record ceiling. We batch Task exports, reassemble them, and import as Pipedrive Activities with type=task. Subject, due date, status, and owner transfer. Any Tasks beyond the 500-record ceiling that are not retrieved in the final export batch are documented as missing and flagged in the reconciliation report.

Nimble custom fields on Contacts and Companies export through CSV as additional columns. We map them to Pipedrive custom fields, matching field types (text to text, date to date, picklist to single-select or multi-select). Boolean fields map to Pipedrive checkboxes. We pre-create all destination custom fields in Pipedrive before loading to avoid import errors from missing field definitions.

Nimble tags are flat label strings on each Contact. We export all tags per record and map them to Pipedrive Labels. Multi-value tag strings (comma-separated) are split into individual Pipedrive Label assignments per Contact. The customer chooses during scoping whether to use Pipedrive Labels or map to a custom multi-select field if the team prefers tag-based segmentation.

Nimble Segments are saved dynamic filters, not standalone exportable objects. We export the constituent Contacts for each segment rather than the segment definition, which has no stable export format. The Contact export includes a source segment tag that allows Pipedrive users to recreate static lists or use Pipedrive's List feature as a replacement.

Nimble message records (outreach history, email log entries) export with recipient, timestamp, type, and message subject. We import these as Pipedrive Notes on the corresponding Person record, with the timestamp preserved. Full email body content does not transfer due to Nimble's storage format constraints and size; we flag this in the discovery report so the customer knows what historical content does not appear in Pipedrive.