Migrate from Nimble CRM to Freshsales

Nimble Contacts map to Freshsales Contacts. Social enrichment fields (LinkedIn, Twitter, Facebook URLs) migrate as custom fields if the destination supports them or as text fields in the Contact record. Email address serves as the dedupe key. We run deduplication against the email field before import to prevent duplicate Contact records.

Nimble Companies map to Freshsales Accounts. Company name becomes the Account Name field and serves as the dedupe key. Accounts must be imported before Contacts so that the Account lookup relationship is satisfied at the moment of Contact insert. We export Companies first, import them into Freshsales, then resolve the AccountId on each Contact by exact name matching during the Contacts phase.

Nimble Deals map to Freshsales Deals with stage, value, owner, and close date. Pipeline stages from Nimble map to Freshsales Deal Stages. Loss/reason fields and custom deal properties migrate as custom fields. Owner resolution happens by email match against Freshsales Users before Deals are inserted.

Nimble's API lacks Task CRUD, so we rely on Nimble's CSV export for Tasks. The 500-record ceiling means large task histories require multiple export requests and reassembly. We chunk export requests, deduplicate across files, and remap task records to Freshsales Task objects with Status, Priority, and ActivityDate preserved. OwnerId resolves by email match against the User table.

Nimble Logged Calls export as Activity records with call type metadata. We map these to Freshsales Task records with the phone call subtype. Call duration and disposition migrate as custom fields if present in the Nimble export. The parent Contact or Company association resolves through the Nimble contact_id or company_id reference by matching against the imported Contact or Account record.

Nimble Events (meetings, appointments) map to Freshsales Event records. Start time, end time, and location migrate directly. Attendee resolution matches email addresses against imported Contact records to populate the Freshsales Event attendee list.

Nimble Notes export as text body content with a parent reference. We map them to Freshsales Note records linked via ContentDocumentLink to the parent Contact, Account, or Deal. Note ordering is preserved by timestamp.

Nimble Custom Data Fields on Contacts and Companies map to Freshsales custom fields on Contact and Account. Field types (text, picklist, date, boolean) are mapped to the equivalent Freshsales field type during schema setup. Freshsales requires custom fields to be created in the destination before import; we pre-create the schema before the data migration phase begins. If a Nimble picklist value has no Freshsales equivalent, we flag it for the customer's admin to resolve before import.

Nimble Tags are flat label associations that export as multi-value fields per Contact. We map them to Freshsales Tags on Contact records. If the destination has tag length or count limits, we trim and consolidate. Tags serve as segmentation signals and do not carry business logic in the destination.

Nimble Workflow definitions have no export path via API or CSV. We do not migrate them. During scoping, we conduct a Workflow audit and document each workflow's trigger conditions and action sequences in a written playbook delivered to the customer's admin for manual rebuild in Freshsales Workflows (Garden tier and above).