Migrate from Lime Go to Microsoft Dynamics 365 Sales

Lime Go Company maps directly to Dynamics 365 Account. Address fields (street, city, postal code, country) translate to the Account.Address1 composite. Multi-address setups in Lime Go (billing vs shipping) require splitting into Account.Address1 and Account.Address2 or creating child records. We recommend consolidating addresses to the primary location during migration to avoid duplicate Account creation.

Lime Go Person maps to Dynamics 365 Contact. The contact's company property becomes Contact.AccountId—a lookup to the parent Account. Lime Go person-to-multiple-companies associations collapse to the primary company link plus Account Contact Relationships in Dynamics 365. If a person has multiple company associations, we preserve the secondary links as Account Contact Relationship records with role designations.

Lime Go Deal maps to Dynamics 365 Opportunity. The deal name becomes Opportunity.Name, amount maps to EstimatedValue, and close date becomes EstimatedCloseDate. The pipeline stage in Lime Go maps to Opportunity.StageName via value mapping against the target Business Process Flow.

Lime Go pipeline definitions translate to Dynamics 365 Business Process Flows. Each pipeline becomes a BPF with stages corresponding to Lime Go stages. BPFs are tied to the Opportunity entity and drive the StageName pick-list values users see when working deals.

Lime Go tasks map to Dynamics 365 Tasks. Subject, description, due date, and priority transfer directly. The regarding object links to the parent Account or Opportunity. Owner resolves by email match to Dynamics 365 user. Recurring task patterns in Lime Go are captured as custom fields on the Task record since Dynamics 365 handles recurrence through the RecurringAppointmentMaster entity.

Lime Go call records become Dynamics 365 PhoneCall activities. Call direction (inbound/outbound) maps to DirectionCode. Subject and duration transfer; phone number stored in PhoneNumber field. Regarding links to the Account or Contact. Call outcomes and notes in Lime Go map to the PhoneCall.Description field and are preserved as part of the activity timeline.

Lime Go meetings map to Dynamics 365 Appointments. Start time, end time, location, and subject transfer. Attendees from Lime Go populate the Appointment's PartyList using Contact or Account lookups matched by email. Meeting body content and attachments migrate to the Appointment's Description field and annotation attachments respectively, maintaining the complete meeting record.

Lime Go notes become Dynamics 365 Annotations. Note text maps to Annotation.NoteText. File attachments in Lime Go download and re-upload to Dynamics 365 SharePoint document management or the Annotation's attachment storage (25MB per file limit applies). Embedded images within notes are preserved as base64 annotations or migrated to SharePoint with a reference link stored in the annotation.

The chronological activity log in Lime Go—calls, emails, meetings, notes in sequence—migrates as individual activity records. The relative ordering and timestamps are preserved; Dynamics 365 displays them in the Timeline control on the Account and Contact forms. Each activity type maintains its specific entity type (PhoneCall, Email, Appointment, Annotation) while preserving the temporal sequence from the original Lime Go timeline.

Any Lime Go custom properties on the Company object become custom columns on the Account table in Dataverse. Field types (text, number, date, pick-list) map to the equivalent Dataverse column type. Pick-list custom fields require value mapping if the options differ between systems.

Lime Go custom properties on Person records migrate as custom columns on the Contact table. Multi-select pick-lists in Lime Go convert to option-set columns in Dynamics 365 with the same value labels preserved for reference. Boolean custom fields map to the TwoOption column type in Dataverse, maintaining the true/false state for each contact record.

Lime Go deal-level custom fields map to custom columns on Opportunity. Currency custom fields in Lime Go use the organization's base currency unless the Dynamics 365 multi-currency model is configured, in which case we map the transaction currency and exchange rate.

Lime Go workflows and automations have no direct equivalent in Dynamics 365 and do not migrate. We export the workflow definitions as a structured JSON reference document so your Dynamics admin can rebuild equivalent logic in Power Automate or Dynamics workflows.

Lime Go's built-in Nordic company enrichment data (3.7 million Nordic business records) does not transfer. We migrate Lime Go's enriched fields as read-only custom text fields on the Account so the data is preserved for reference even without active enrichment in Dynamics 365.

Lime Go owner assignments resolve by email matching against Dynamics 365 SystemUser records. Unmatched owners are flagged before migration; your team either provisions a Dynamics user first or assigns to a fallback owner. Owner history is preserved as a custom audit field on migrated records.