Migrate from Nimble CRM to HighLevel

Nimble Contact records map to GoHighLevel Contact records. Standard fields (name, email, phone, address, company) map directly. Social enrichment fields (LinkedIn URL, Twitter URL, Facebook URL) from Nimble have no GoHighLevel native equivalent; we create Contact custom fields for each social URL and migrate the values so the enrichment data is preserved even though the automatic enrichment feature does not carry over. Contact custom fields in GoHighLevel are locked to Contact type after creation, so the field partition is designed during scoping before migration.

Nimble Company records map to GoHighLevel Contact records with the Organization toggle enabled. The Nimble Company name becomes the Contact organization name. We export Companies first and use exact name matching to associate Nimble Company IDs with GoHighLevel Contact organization lookups during the Contact import phase. If the customer uses Nimble's Company object heavily, we discuss whether Company records should become separate GoHighLevel Custom Objects instead, which requires pre-creation of the Custom Object schema before migration.

Nimble Deal records map to GoHighLevel Opportunities. Deal fields (name, value, stage, owner, close date, loss reason) map to GoHighLevel Opportunity fields. We pre-create the GoHighLevel pipeline with stages that correspond to Nimble's deal stages, mapping stage names and probabilities. The deal owner maps by email match to a GoHighLevel User. Loss reason and notes migrate as Opportunity custom fields.

Nimble custom fields exist on Contacts and Companies with types including text, picklist, date, boolean, and number. We partition the field set during scoping: fields that describe the person (lead source, birthday, preferred contact method) become GoHighLevel Contact custom fields; fields that describe the deal (budget, timeline, property type) become GoHighLevel Opportunity custom fields. Once a GoHighLevel field is created as Contact or Opportunity type, it cannot be switched. This partition decision is made before any data moves and drives the pre-migration schema setup.

Nimble Tasks export via CSV (the Nimble API lacks Task CRUD). CSV exports are capped at 500 records per email-delivered file, so large task histories require multiple export requests and reassembly before import. We migrate Task title, status (open/closed), due date, owner, and notes as GoHighLevel Task fields. The activity date preserves the original Nimble timestamp for timeline ordering.

Nimble logged call records map to GoHighLevel Tasks with the call disposition and duration preserved in custom fields. Call recordings are not migratable from Nimble; we flag this in the discovery report and recommend the customer download any recordings from Nimble before the migration window.

Nimble Event records map to GoHighLevel Appointments. Subject, start and end time, location, and attendee list migrate. Attendee resolution uses email matching to existing GoHighLevel Contact records; unmatched attendees are logged as text notes on the appointment.

Nimble flat tags on Contacts migrate to GoHighLevel Tags. Multi-value tag fields from Nimble map to GoHighLevel tags with each tag value becoming a separate tag record linked to the Contact. Tags used for segmentation are preserved for post-migration Smart List and workflow triggers.

Nimble Segments are saved dynamic filters, not standalone exportable objects. We export the constituent contacts from each segment and tag them with the segment name, then rebuild the equivalent filter as a GoHighLevel Smart List using the migrated tag and field values. If a segment definition is complex, we document the filter criteria for manual rebuild.

Nimble attachments are stored within the 2GB per-user storage limit and may include contact documents, deal files, and images. Full binary attachment migration is not included. We extract attachment metadata (filename, file type, associated record) and migrate it as a GoHighLevel Note with a reference to external storage if the customer has a cloud storage URL, or as a text note documenting the original filename for manual re-upload. Attachments approaching the Nimble storage limit are flagged during scoping.