CRM migration
Field-level mapping, validation, and rollback between Lime CRM and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
Lime CRM
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
8 of 8
objects map 1:1 between Lime CRM and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Lime CRM to Microsoft Microsoft Dynamics 365 Sales is a schema-first migration. Lime CRM organises data around configurable Limetypes that each organisation defines differently, meaning no two tenants share the same canonical schema. We must export the live schema definition from the customer's Lime CRM admin before any field mapping begins, then design the Microsoft Dynamics 365 Sales target schema with matching custom fields, lookup relationships, and Sales Processes. Email conversations export from Lime CRM as individual message files rather than threaded records; we reassemble them by conversation ID and timestamp during transformation so the migration does not arrive as disconnected messages. Workflow Automations defined in Lime CRM cannot be exported as machine-readable files; we document the rule logic and deliver it as a written inventory for reconstruction in Microsoft Dynamics 365 Sales Process Builder or Power Automate. Microsoft Dynamics 365 Sales Professional starts at $65 per user per month with unlimited pipelines and custom objects from the Professional tier, addressing the feature-depth ceiling that Nordic mid-market teams cite as they scale beyond 50 to 200 users.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
Lime CRM platform overview
Scorecard, SWOT, gotchas, and pricing for Lime CRM.
Destination platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Data migration guide
The complete Microsoft Dynamics 365 Sales migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Microsoft Dynamics 365 Sales migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Sales .
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Lime CRM object lands in Microsoft Dynamics 365 Sales , including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Lime CRM
Company
Microsoft Dynamics 365 Sales
Account
1:1Lime CRM Company records map to Dynamics 365 Account. The Organisation Number from Lime CRM becomes the Account Number field and functions as a dedupe key during import. We preserve the Industry, Website, and Address fields directly. Account is imported before any Contact import so that the Parent Account lookup and Contact.AccountId reference are satisfied at the moment of Contact insert.
Lime CRM
Contact
Microsoft Dynamics 365 Sales
Contact
1:1Lime CRM Contact records map to Dynamics 365 Contact. FirstName, LastName, Email, Phone, and custom fields migrate directly. Phone number formats are normalised to prevent leading-zero stripping that commonly occurs in CSV-based imports. We preserve any Lime CRM Contact relationship to a Company via the AccountId lookup and validate that the parent Account exists before Contact import begins.
Lime CRM
Deal
Microsoft Dynamics 365 Sales
Opportunity
1:1Lime CRM Deal records map to Dynamics 365 Opportunity. Deal value, stage, owner, expected close date, and custom properties migrate to the Opportunity schema. Lime CRM's custom deal pipelines and industry-specific stages map to Microsoft Dynamics 365 Sales Process and Record Type configurations that we deploy before migration. Closed-Lost and Closed-Won reason fields from Lime CRM custom properties become Dynamics Opportunity CloseReason values.
Lime CRM
Activity: Call
Microsoft Dynamics 365 Sales
Task (TaskTypeCode = PhoneCall)
1:1Lime CRM logged calls map to Dynamics 365 Task with TaskTypeCode = PhoneCall. Call duration, disposition, and owner information transfer to custom Task fields. We preserve the parent Contact and Account relationship via the RegardingObjectId lookup so the call appears in the correct activity timeline.
Lime CRM
Activity: Meeting
Microsoft Dynamics 365 Sales
Appointment
1:1Lime CRM meeting records map to Dynamics 365 Appointment. Start, End, Location, and Description fields migrate directly. We create an ActivityParty record for each attendee linking the meeting to the relevant Contact or Account records in Dynamics 365.
Lime CRM
Activity: Note
Microsoft Dynamics 365 Sales
Annotation
1:1Lime CRM Notes attached to Contacts, Companies, or Deals map to Dynamics 365 Annotation records. Note text and any embedded file attachments migrate as separate Note and FileAttachment records linked via the ObjectId and ObjectTypeCode references. We preserve the original created date and author information from Lime CRM.
Lime CRM
Ticket
Microsoft Dynamics 365 Sales
Case
1:1Lime CRM Ticket records migrate to Dynamics 365 Case if the destination org includes Dynamics 365 Customer Service or Sales Enterprise. Ticket status, priority, and assignee map to Case Status, Priority, and OwnerId. The conversation history on each Ticket requires reassembly from individual message files (see Email threads gotcha) and is attached to the Case as EmailActivity records.
Lime CRM
Custom Object (Limetype)
Microsoft Dynamics 365 Sales
Custom Entity
1:1Lime CRM's configurable Limetypes map to Dynamics 365 custom entities on Dataverse. Each custom Limetype requires field-level mapping because the schema varies per customer implementation. We export the live schema definition from the customer's Lime CRM admin before mapping begins, pre-create the destination custom entity with matching field types and lookups, and treat each custom Limetype as a separate migration workstream with its own dependency chain.
| Lime CRM | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Company | Account1:1 | Fully supported | |
| Contact | Contact1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Activity: Call | Task (TaskTypeCode = PhoneCall)1:1 | Fully supported | |
| Activity: Meeting | Appointment1:1 | Fully supported | |
| Activity: Note | Annotation1:1 | Fully supported | |
| Ticket | Case1:1 | Fully supported | |
| Custom Object (Limetype) | Custom Entity1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Lime CRM gotchas
Email threads export as individual message files
Super API-key generation removed from API
Custom Limetype schema is customer-unique
No bulk export for attachments in base tier
Workflow Automations do not export in transferable format
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
Pair-specific challenges
Migration approach
Discovery and schema extraction
We audit the source Lime CRM portal to inventory Companies, Contacts, Deals, Activities, Tickets, and any custom Limetypes. We extract the live schema definition from the customer's Lime CRM admin to understand every custom field, lookup relationship, and picklist value set. We pair this with the Dynamics 365 destination org audit to inventory existing custom entities, validation rules, and field-level security. The discovery output is a written migration scope with per-object record counts, a field-level mapping matrix, and a Microsoft Dynamics 365 Sales edition recommendation based on the customer's data complexity.
Schema design and Sales Process configuration
We design the Dynamics 365 target schema with matching custom fields and lookup relationships for every Lime CRM Limetype. This includes creating custom entities in the destination org, configuring Record Types and Sales Processes to match Lime CRM's industry-specific pipeline stages, and mapping picklist values to Dynamics Option Set values. Schema is deployed to a Dynamics 365 Sandbox environment first for validation before any production migration begins.
Sandbox migration and reconciliation
We run a full migration into the Dynamics 365 Sandbox using production-like data volume. The customer's RevOps or system administrator reconciles record counts across all objects, spot-checks 25-50 random records against the Lime CRM source, and validates that custom field values, lookup relationships, and activity timelines are correctly populated. Any mapping corrections happen in the Sandbox phase before production migration proceeds.
Owner reconciliation and User provisioning
We extract every distinct Lime CRM Owner referenced on Contact, Company, Deal, and Activity records and match by email against the Dynamics 365 destination org's User table. Owners without a matching User go to a reconciliation queue. The customer's Dynamics 365 admin provisions any missing Users and assigns the appropriate Security Roles before record import resumes. Migration cannot proceed past this step because OwnerId references are required on most standard entities.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Lime CRM Companies), Contacts (with AccountId resolved), Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Activities (Tasks, Appointments, Notes via batch API with parent-record resolution), Cases (with conversation history reassembled from individual message files), and Custom Entities (last because they often have lookups to standard entities). Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and automation handoff
We freeze Lime CRM writes during cutover, run a final delta migration of any records modified during the migration window, then enable Microsoft Dynamics 365 Sales as the system of record. We deliver the Workflow Automation inventory document to the customer's admin team with a written map of each Lime CRM automation rule and its recommended Dynamics 365 Power Automate or Process Builder equivalent. We support a one-week hypercare window where we resolve any reconciliation issues. We do not rebuild Lime Workflow Automations as Dynamics 365 flows inside the migration scope; that is a separate engagement.
Platform deep dives
Lime CRM
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between Lime CRM and Microsoft Dynamics 365 Sales .
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Lime CRM and Microsoft Dynamics 365 Sales .
Object compatibility
All 8 core objects map 1:1 between Lime CRM and Microsoft Dynamics 365 Sales .
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Lime CRM: Not publicly documented.
Data volume sensitivity
Lime CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Lime CRM to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your Lime CRM to Microsoft Dynamics 365 Sales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Lime CRM
Other ways to arrive at Microsoft Dynamics 365 Sales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.
