Migrate from Nimble CRM to Salesforce Sales Cloud

Nimble's flat Contact model has no direct Salesforce equivalent because Salesforce separates unqualified prospects (Lead) from qualified buyers (Contact attached to Account). We define a split rule during scoping based on the customer's criteria (email domain, social profile presence, or deal history). Contacts with associated Deals and Company links become Salesforce Contacts on an Account. Contacts without Company associations and without deal history are loaded as Salesforce Leads for qualification review. The original Nimble contact record is preserved in a custom field nimble_original_id__c for cross-reference.

Nimble Company records map directly to Salesforce Account. Company name becomes Account Name (the dedupe key during import). We export Companies first and remap by exact name on import into Salesforce so that Contact imports can resolve AccountId at insert time. Website, industry, phone, and address fields map to standard Account fields. Social URLs (LinkedIn Company page) from Nimble migrate to a custom field social_url__c since Salesforce has no native social enrichment fields.

Nimble Deals map to Salesforce Opportunity. The Nimble deal stage maps to Salesforce StageName; we configure the Salesforce Sales Process before migration to whitelist the relevant stage values. Close date, deal value, owner, and Company association migrate directly. Loss reason fields in Nimble custom fields map to Salesforce Loss Reason custom field. Stage probability percentages are set per-stage during Salesforce configuration.

Nimble Task records require a workaround because the API lacks Task CRUD. We use Nimble's CSV export (capped at 500 records per email-delivered file) and batch multiple export requests for large databases. Each exported CSV file is reassembled and deduplicated before mapping to Salesforce Task fields: Subject, Status, Priority, ActivityDate, and Description. Owner resolution happens by email match to Salesforce User. High-volume task migrations (over 50,000 records) use the Salesforce Bulk API 2.0 rather than Data Loader.

Nimble logged calls export via CSV with call duration, disposition, and timestamp fields. We map these to Salesforce Task with TaskSubtype=Call, CallDurationInSeconds, and CallDisposition preserved as custom Task fields. Activity timeline ordering is preserved by setting ActivityDate to the original Nimble call timestamp.

Nimble Events (meetings) map to Salesforce Event with StartDateTime, EndDateTime, Subject, and Location preserved. Attendee email lists from Nimble export are linked to Salesforce EventRelation records pointing at the resolved Contacts or Leads.

Nimble Custom Data Fields on Contacts and Companies are exported via CSV with their column headers intact. We map field types: text fields to Salesforce Text (255), long text to Long Text Area, date fields to Date, boolean checkboxes to Checkbox, and picklist values to Picklist or Multi-Select Picklist depending on how Nimble stored the data. Salesforce custom fields are pre-created in the destination org before migration begins; field-level security is set for the migration user during the data load phase.

Nimble tags are flat label associations stored as comma-separated values per contact. Multi-value tag fields require splitting during transformation if the destination is a Salesforce single-select picklist. We present two strategies during scoping: migrate to a Salesforce Multi-Select Picklist field (preserves all tags on one field) or map to Salesforce Topics with TopicAssignment records (better for content classification use cases). The customer chooses; we implement both in sandbox before committing to production.

Nimble Segments are saved dynamic filters, not standalone objects, and have no stable export format. We export the constituent Contacts for each segment rather than the segment definition. In Salesforce, the exported contacts are associated via a Campaign membership (dynamic lists map to Campaign Member Status = Sent/Responded for segmentation) or tagged with a custom segment field for reporting filtering.

Nimble Message records store outreach history (recipient, timestamp, type: email/sequence) and are partially exportable via CSV. We capture recipient, timestamp, and type but do not migrate full email body content due to storage format and attachment handling complexity. Messages migrate as Salesforce Task records (Subject: outreach type, ActivityDate: timestamp) with a custom field nimble_message_type__c. Full email body migration is out of scope.

Nimble attachments are stored within the 2GB per-user storage limit and may be partially consumed before migration. We extract attachment metadata (filename, MIME type, record association) via CSV export and re-link files from external storage where the customer has maintained backups. Full binary attachment migration is not included by default; we recommend the customer exports attachments separately before migration and re-uploads to Salesforce Files or ContentWorkspace post-migration.

Nimble Workflow definitions (kanban-based automation triggers and actions) are not accessible via CSV or API and have no export path. We do not migrate Workflows. During discovery we conduct a Workflow audit, document each workflow's trigger conditions and action sequences, and deliver a written playbook so the customer's admin can rebuild automations in Salesforce Flow. Workflow rebuild is outside migration scope and is a separate engagement or internal admin task.