Migrate from Lime Go to Nutshell

Lime Go Customers (company-level records) map to Nutshell Company records. Lime Go Customer properties including company name, address, phone, industry, custom fields, and tags migrate to the corresponding Nutshell Company fields. If the customer uses Lime Go's unified Customer-Contact model without separate Company records, we create Nutshell Company records from the Customer data and link them to Person records. The Lime Technologies move-to-go tool also supports Organizations as a separate entity from Persons, which aligns with Nutshell's Company distinction.

Lime Go Contacts map to Nutshell People records. Full field fidelity is preserved including first name, last name, email, phone, title, custom properties, owner assignment, and GDPR consent flags. Nutshell's People record can serve as both individual contact and organizational representative. We resolve the link to the Nutshell Company record that was created from the corresponding Lime Go Customer using domain-based matching or explicit company name matching.

Lime Go visual adjustable sales pipelines with configurable stages map to Nutshell's pipeline structure. We preserve stage names, order, and probability settings during migration. If Lime Go has multiple pipelines configured, these map to separate Nutshell pipelines or to pipeline stages within a single Nutshell pipeline depending on the customer's chosen Nutshell plan tier.

Lime Go Deals map to Nutshell Deals or Leads depending on deal stage and customer preference. Active sales deals map to Nutshell Deals with value, expected close date, owner, and linked Company/Person preserved. Deals that are early-stage prospect entries can map to Nutshell Leads if the customer prefers to use Nutshell's Lead object for early pipeline entries. Closed-won and closed-lost deal history migrates with stage history preserved as deal activity.

Lime Go Activities (touchpoints logged against Customers, Contacts, or Deals) map to Nutshell Tasks or Notes depending on activity type. Phone calls map to Tasks with call disposition preserved; meetings map to Tasks with attendee information; general touchpoints map to Notes attached to the corresponding Person or Company. Activity timestamps and author information migrate to preserve the timeline view in Nutshell.

Lime Go Tasks including assignee, due date, status, priority, and description migrate to Nutshell Tasks. Lime Go's limitation on batch task operations does not affect how we structure migrated records. Open tasks migrate with their current status; completed tasks migrate with completion timestamps. Recurring tasks in Lime Go map to Nutshell repeating tasks where the destination platform supports them.

Lime Go Reminders attached to Contacts, Customers, or Deals map to Nutshell Tasks with the reminder timestamp preserved as the task due date. The notification context (linked record type and ID) migrates as a link to the corresponding Nutshell Person or Company. Recurring reminders in Lime Go map to Nutshell repeating tasks.

Lime Go History Notes (chronological interaction records per Customer or Contact) map to Nutshell Notes attached to the corresponding Person or Company record. Full note text, author, timestamp, and any associated attachments migrate. Attachments to history notes become Nutshell file attachments on the Note record or linked ContentDocument records.

Documents attached to Lime Go Customers, Contacts, or Deals are extracted and linked to the corresponding Nutshell Person, Company, or Deal record. File names, upload timestamps, and file types are preserved. Large binary files (over 10MB) may require chunked upload handling depending on Nutshell's attachment API limits at the time of migration.

Lime Go custom fields on Customers, Contacts, and Deals vary by tenant. We discover the tenant schema during scoping, map field types (text, number, date, picklist, checkbox) to Nutshell custom field equivalents. A known limitation: Nutshell's API does not support searching by custom field value, which affects post-migration data auditing workflows. We flag this during scoping so the customer can plan alternative data lookup processes. Unmapped custom field types are documented for admin review.