Migrate from Lime Go to Zoho CRM

Lime Go Customers store company-level data with contact associations. We map Customers to Zoho Accounts 1:1, preserving company name, address, custom fields, tags, and owner assignments. If the customer's Lime Go instance contains unqualified prospect records that should not yet be Account-assigned Contacts, we split them into Zoho Leads during scoping based on a Customer property (e.g., status or stage) agreed upon before migration. The original Lime Go Customer status is preserved as a custom field lg_original_status__c for audit and reporting in Zoho.

Lime Go Contacts map to Zoho Contacts with full field fidelity. Email, phone, custom properties, GDPR consent flags, and owner assignments transfer as typed Zoho fields. The Contact-Account relationship resolves at migration time using the parent Customer mapping. Lime Go's contact-level GDPR consent history (granted, withdrawn, timestamps) migrates to custom Contact fields or a linked custom GDPR Consent module that we configure during schema design.

Each Lime Go Sales Pipeline maps to a Zoho CRM pipeline structure. We create Zoho pipeline stages corresponding to Lime Go deal stages, preserving stage order, names, and probability percentages. Stage probabilities round to Zoho's supported integer range. If Lime Go pipelines use custom colors or layouts, we document these for recreation as Zoho Blueprint stages and layouts.

Lime Go Deals map to Zoho Deals with deal name, value, expected close date, owner, pipeline stage assignment, and custom fields preserved. The Deals-Accounts Lookup resolves at migration time using the Customer-to-Account mapping. Historical stage transitions from Lime Go migrate as Zoho Deal Activities or custom stage-history fields depending on the depth of pipeline history required.

Lime Go Activities (meeting, call, task, email touchpoints) map to Zoho CRM Activities. Meeting-type activities become Zoho Events with Start DateTime and End DateTime; call activities become Zoho Tasks with Call type subtype; general tasks become Zoho Tasks. Activity-linked Contact and Customer references resolve via the Contact and Account mappings established earlier in the migration sequence.

Lime Go Tasks with assignee, due date, status, and priority migrate to Zoho Tasks. Task ownership resolves via the User-email lookup. Batch action limitations in Lime Go do not affect how we structure migrated task records; each Lime Go task becomes a discrete Zoho Task. Recurring Lime Go tasks map to Zoho recurring Task patterns where the recurrence rule is parseable from the source data.

Lime Go Reminders attached to Contacts, Customers, or Deals migrate as Zoho Tasks with the reminder timestamp preserved in the Zoho Task Due Date and a custom lg_reminder_datetime__c field for audit. Reminder recurrence patterns map to Zoho recurring Task configurations where supported.

Lime Go History Notes (chronological interaction records per Customer or Contact) migrate to Zoho Notes linked via ContentDocumentLink to the parent Contact or Account record. Note author, timestamp, and body text preserve. Rich text formatting in Lime Go notes converts to Zoho's supported rich text subset. Attachments embedded in notes migrate as separate ContentDocument records linked to the same parent.

Lime Go documents attached to Customers, Contacts, or Deals extract as files and load into Zoho as ContentDocument records via Zoho's API attachment endpoint. We preserve original file names, upload timestamps, and the parent record linkage. Large binary attachments (>25 MB per Zoho limit) require chunked upload handling or alternative storage references. We flag any files exceeding Zoho's size limit during scoping.

Lime Go custom fields on Customers, Contacts, and Deals vary by tenant schema. We discover the tenant schema during scoping, map field types (text, number, date, picklist) to Zoho equivalent field types (Single Line, Multi Line, Currency, Date, Pick List, Multi-Select Pick List), and flag any field types with no Zoho equivalent for manual handling. Custom field display names preserve; API names follow Zoho's lowercase-underscore naming convention. Zoho's 500-field-per-module limit applies at all tiers.

Lime Go tags apply across Customers, Contacts, and Deals for segmentation. We preserve tag values as flat arrays and map them to Zoho custom multi-select picklist fields on the relevant module. During scoping, the customer chooses whether tags migrate as a Zoho native Multi-Select Picklist or as a custom Tag module with lookups to other modules. The tag vocabulary is preserved as picklist values in Zoho.

Lime Go's GDPR consent history (consent granted, consent withdrawn, timestamps, source of consent) has no native Zoho CRM equivalent. We reconstruct this as custom Contact and Account fields (e.g., lg_consent_source__c, lg_consent_date__c, lg_consent_withdrawn__c) and optionally a linked GDPR Consent custom module if the customer requires a full consent timeline audit trail. Anonymisation flags migrate as a boolean custom field for administrative reference.