Migrate from Nimble CRM to Twenty CRM

Nimble Contacts map to Twenty Persons. The Contact's name, email, phone, address, social profiles (LinkedIn, Twitter, Facebook URLs), and any Custom Data Fields transfer via CSV export and bulk import. Nimble's social enrichment URLs are stored as text fields on the Person record in Twenty; they do not receive live enrichment. We resolve the parent Organization by exact name matching from the Nimble Company field to preserve the Person-to-Organization relationship.

Nimble Companies map to Twenty Organizations. The company name, domain, industry, address, phone, and any Custom Data Fields transfer. We export Organizations first in the migration sequence to ensure that the Organization exists before any Person import that references it. Name-based lookup resolution is the primary dedupe mechanism; domain is stored as the website field and used as a secondary dedupe signal.

Nimble Deals map to Twenty Opportunities. Deal name, value, stage, owner, expected close date, and loss reason fields transfer. Nimble's pipeline stages map to Twenty's Opportunity stage labels, which we configure before migration. Closed-Won and Closed-Lost reasons from Nimble custom fields map to Twenty's lossReason field if present, or to a custom text field for manual categorization in Twenty.

Each Nimble deal pipeline and its associated stage values are documented during scoping and configured in Twenty as Opportunity stages with custom labels. Stage probability weights are set per stage in Twenty's pipeline configuration. The customer chooses whether to replicate Nimble's stage set exactly or consolidate during migration for a cleaner Twenty pipeline.

Nimble Task records export via CSV with a hard ceiling of 500 records per export file. Large task histories require multiple export requests and reassembly before import into Twenty. We flag any Tasks beyond the export ceiling as a written inventory item for manual follow-up. Task subject, status, due date, and assignment transfer; body text migrates as the Task description field.

Nimble Logged Calls map to Twenty Tasks with the call subject and duration preserved. Call disposition and notes transfer to the Task description. We extract the call timestamp and set it as the Task due date or a custom activity timestamp field in Twenty. Call recording URLs are not natively transferable and are flagged as a manual-rebuild item if the customer uses call recording.

Nimble Events map to Twenty Tasks with the event title, start and end timestamps, and location preserved. Attendee information transfers as a comma-separated list in a custom text field in Twenty since Twenty does not have a native EventAttendee model in the same way as Salesforce. Meeting notes migrate as the Task description.

Nimble Custom Data Fields on Contacts map to custom fields on the Person object in Twenty. Field types (text, picklist, date, boolean, number) are mapped to equivalent Twenty field types during the schema setup phase. Picklist values are recreated as options in Twenty's field configuration. We export custom field definitions from Nimble during scoping and pre-create the corresponding fields in Twenty before any Person import.

Nimble tags (flat label associations on Contacts and Companies) transfer as tags on the equivalent Twenty record. Multi-value tag fields may need splitting if Twenty's tagging model requires single-tag-per-association on bulk import. We export all tags per record as a comma-separated string in a custom field for initial import, then create native tag assignments from that field. Tag strategy is confirmed with the customer during scoping.

Nimble Owners (users assigned to Contacts, Companies, and Deals) map to Twenty Users. We resolve owners by email match during import. Any Nimble Owner without a matching Twenty User is held in a reconciliation queue for the customer's admin to provision the Twenty User before record import resumes. Owner assignment on Opportunities transfers by email lookup.

Nimble message records store outreach history including recipient, timestamp, and type (email/sequence). Full email body content may not transfer cleanly due to HTML formatting differences and storage constraints. We capture recipient, timestamp, and type as a Note on the Person record in Twenty. Full message body migration is scoped as a separate effort if the customer requires it.

Attachments stored within Nimble's 2GB per-user storage limit are extracted as metadata and re-linked where possible. Full binary attachment migration is not included by default due to the storage constraint on the source side. We document attachment count and total size during scoping and flag any attachments at risk of being lost due to the storage ceiling.