Migrate from Lime Go to Salesforce Sales Cloud

Lime Go Customers (the primary account-level records storing company data, metadata, and ownership) map directly to Salesforce Account. We preserve custom fields, tags, and the Customer ID as an External ID for deduplication. Lime Go's visual company data and owner assignments map to Account Name, Industry, Type, and OwnerId. This is the first object loaded because all downstream Contact and Deal records reference the Account.

Lime Go Contacts (individual people linked to Customers) map to Salesforce Contact with full field fidelity: name, email, phone, title, custom properties, and owner assignments. The Lime Go Customer-to-Account link resolves to AccountId during import. GDPR consent flags migrate as custom Contact fields (consent_type__c, consent_date__c, consent_withdrawn__c) preserving the full consent timeline for Nordic data protection compliance.

Lime Go's built-in Nordic company database of 3.7 million businesses is a read-only enrichment layer, not user-owned CRM data. It does not migrate as Accounts or Contacts. We extract these records as enrichment context files and flag them separately during scoping. The customer retains Lime Go for prospecting enrichment or selects a Salesforce-native enrichment provider (Data Cloud, DiscoverORG, Clearbit) post-migration. This prevents customers from expecting 3.7 million records to populate their Salesforce org.

Lime Go's configurable pipeline stages map to a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the stage values. Stage order, names, and probability percentages migrate from Lime Go's pipeline configuration to Salesforce StageName and StageProbability. Lime Go's single pipeline maps to one Record Type; additional pipelines would require additional Record Types and Page Layouts.

Lime Go Deals linked to Customers map to Salesforce Opportunity with AccountId resolved, OwnerId matched by email, and RecordTypeId assigned from the pipeline configuration. Deal value, expected close date, stage (mapped via pipeline configuration), and custom fields preserve. Historical stage movements and closed-lost/closed-won timestamps migrate as Opportunity Field History records if Salesforce Shield is enabled.

Lime Go Activities (touchpoints logged between users and records) map to Salesforce Task for call logs and to-dos, and Event for scheduled meetings. Activity type, timestamp, subject, body, and linked Contact or Customer WhoId/WhatId resolve during migration. We use Bulk API 2.0 for large activity volumes with parent-record lookup resolution.

Lime Go Tasks migrate to Salesforce Task with assignee (OwnerId resolved by email match), due date (ActivityDate), status (Status), and priority preserved. Batch action limitations in Lime Go do not affect migration; each Task migrates individually. Task ownership resolves via the User mapping established during scoping.

Lime Go Reminders attached to Contacts, Customers, or Deals map to Salesforce Task records with the reminder timestamp preserved as ActivityDate and a custom reminder_type__c field distinguishing them from standard tasks. Recurring reminders migrate as individual Task records with a recurrence pattern field added.

Lime Go History Notes (chronological interaction records per Customer or Contact) migrate to Salesforce Task with TaskSubtype = Log a Call for timestamped activities, or Salesforce Note for freeform annotated entries. Author, timestamp, full note text, and any linked attachments preserve. Note body migrates as rich text.

Lime Go documents attached to Customers, Contacts, or Deals migrate as Salesforce Files (ContentDocument and ContentVersion records). We extract files from Lime Go storage, upload to Salesforce, and link via ContentDocumentLink to the corresponding Account, Contact, or Opportunity. Large binary files may require chunked upload handling. File names and original upload timestamps preserve in Salesforce metadata.

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) to Salesforce field types (Text, Number, Date, Picklist), and create the destination custom fields via metadata API before record import. Unmapped field types are flagged in the scoping document for the customer admin to review.

Lime Go tags applied across Customers, Contacts, and Deals migrate as flat label arrays. We map them to Salesforce multi-select picklist fields on the respective objects, or to a custom Tag__c junction object with lookup relationships if the customer prefers normalized tagging. The customer chooses the tag strategy during scoping.

Lime Go consent history (granted, withdrawn, timestamps, and external sharing flags) migrates as custom Contact and Account fields to maintain GDPR compliance posture in Salesforce. We preserve the full consent timeline as structured custom fields: consent_source__c, consent_granted_date__c, consent_withdrawn_date__c, and data_retention_policy__c. This is critical for Nordic customers subject to GDPR and Swedish data protection law.

Lime Go users referenced on Customers, Contacts, Deals, Activities, and Tasks map to Salesforce User records by email match. We extract every distinct owner from Lime Go records during scoping, cross-reference against the destination Salesforce org's User table, and hold any unmatched owners in a reconciliation queue for the customer's admin to provision before record import resumes.