CRM migration
Field-level mapping, validation, and rollback between Optimiser CRM and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
Optimiser CRM
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
9 of 12
objects map 1:1 between Optimiser CRM and Microsoft Dynamics 365 Sales .
Complexity
CModerate
Timeline
4-8 weeks
Overview
Moving from Optimiser CRM to Microsoft Microsoft Dynamics 365 Sales is a multi-step migration constrained by Optimiser's lack of a documented public API. We extract data through the platform's built-in CSV export utility, which requires pagination across multiple export runs for datasets exceeding the per-run record limit. Microsoft Microsoft Dynamics 365 Sales uses the Account-Contact-Opportunity model with a separate Lead object, so we evaluate whether Optimiser's contact records should split into Leads and Contacts or merge directly into Contacts attached to Accounts based on qualification status. Activity history (calls, emails, meetings, notes) migrates into Microsoft Dynamics 365 Sales Tasks, Events, and EmailMessage records with parent-record resolution against the imported Contacts and Accounts. Workflows, assignment rules, and triggered sequences built in Optimiser do not migrate; we deliver a written rebuild checklist mapped to Dynamics Sales accelerator templates and Power Automate flows. Pricing for Microsoft Dynamics 365 Sales starts at $65 per user per month for Sales Professional and $105 per user per month for Sales Enterprise, with the Team Member license at $8 per user per month for read-only access.
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
Optimiser CRM platform overview
Scorecard, SWOT, gotchas, and pricing for Optimiser 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 Optimiser 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.
Optimiser CRM
Contact
Microsoft Dynamics 365 Sales
Contact
1:1Optimiser CRM Contacts map to Microsoft Dynamics 365 Sales Contact records. Standard fields (FullName, EmailAddress, BusinessPhone, MailingAddress) transfer directly. We enumerate every Optimiser custom field during scoping via trial export, create matching custom fields in Microsoft Dynamics 365 Sales (using the field name as the display label with a custom field prefix), and map values before import. Contacts without a parent Account receive a placeholder Account during migration or are linked to an Account by domain match on the email address.
Optimiser CRM
Company
Microsoft Dynamics 365 Sales
Account
1:1Optimiser CRM Company records map to Microsoft Dynamics 365 Sales Account. CompanyName maps to Account Name; website domain maps to Website. We resolve duplicate Accounts by name and domain before import using a staging dedupe pass. Account is imported before Contact so that the ParentAccountId Lookup relationship is satisfied at Contact insert time.
Optimiser CRM
Deal
Microsoft Dynamics 365 Sales
Opportunity
1:1Optimiser CRM Deals map to Microsoft Dynamics 365 Sales Opportunity. Deal stage names extracted from the Optimiser instance map to a Dynamics Sales Process stage via a stage-mapping table we build during scoping. Deal value maps to Amount, expected close date maps to CloseDate, and owner assignment maps via email lookup to the Dynamics User record. Closed-Lost and Closed-Won states from Optimiser translate to the corresponding Opportunity StageName values.
Optimiser CRM
Pipeline Stage
Microsoft Dynamics 365 Sales
Stage + Sales Process
lossyOptimiser's configurable pipeline stages export as a distinct list per instance. We create a Microsoft Dynamics 365 Sales Sales Process that mirrors the Optimiser stage sequence, whitelists the imported stage values in the sales process, and sets probability percentages per stage. If the customer uses multiple pipelines in Optimiser, we create corresponding Record Types in Microsoft Dynamics 365 Sales with separate Sales Processes per Record Type.
Optimiser CRM
Lead
Microsoft Dynamics 365 Sales
Lead
1:1Optimiser Lead records (status, source, score fields) map to Microsoft Dynamics 365 Sales Lead. We evaluate whether Optimiser Leads represent unqualified prospects (map to Lead) or should be treated as already-qualified records (map to Contact attached to Account) based on their status field value. Lead score from Optimiser migrates to a custom integer field lead_score__c in Microsoft Dynamics 365 Sales . Lead Status values map to the configured Dynamics Lead Status picklist.
Optimiser CRM
Activity: Call
Microsoft Dynamics 365 Sales
Task (TaskSubtype = Call)
1:1Optimiser call logs export as activity records with type, duration, disposition, and timestamp. Calls migrate to Microsoft Dynamics 365 Sales Task records with TaskSubtype = Call, CallDurationInSeconds, and CallDisposition preserved in custom Task fields. ActivityDate is set to the original Optimiser timestamp to preserve chronological ordering in the timeline.
Optimiser CRM
Activity: Email
Microsoft Dynamics 365 Sales
EmailMessage + Task
1:1Optimiser email engagements migrate to Microsoft Dynamics 365 Sales EmailMessage records (the message content) linked to an Activity Task record (the timeline entry). The regarding (WhatId) points to the related Contact or Opportunity. Email subject, body, from, and to addresses transfer directly. Attachments download locally and re-upload to Dynamics SharePoint or as EmailAttachment records linked to the EmailMessage.
Optimiser CRM
Activity: Meeting
Microsoft Dynamics 365 Sales
Event
1:1Optimiser meeting records migrate to Microsoft Dynamics 365 Sales Event with Subject, StartDateTime, EndDateTime, Location, and optional description preserved. Attendee lists from Optimiser create EventRelation records linked to the corresponding Contact or Lead. Virtual meeting links preserve as Location or as a custom field.
Optimiser CRM
Activity: Note
Microsoft Dynamics 365 Sales
Annotation
1:1Optimiser Notes migrate to Microsoft Dynamics 365 Sales Annotation records (the Note body) linked via objectid to the parent Contact, Account, or Opportunity. Rich text formatting is preserved where the export supports it. Image attachments migrate as FileAttachment records linked to the Annotation.
Optimiser CRM
User/Owner
Microsoft Dynamics 365 Sales
User
1:1Optimiser User records (name, email, role) map to Microsoft Dynamics 365 Sales User records via email address match. We extract every distinct owner referenced on Contact, Account, Deal, and Activity records and cross-reference against the destination org's User table. Any Optimiser owner without a corresponding Dynamics User is placed in a reconciliation queue for the customer's admin to provision before record import resumes.
Optimiser CRM
Document
Microsoft Dynamics 365 Sales
SharePoint Document or File
lossyDocument attachments referenced by URL or stored in Optimiser's file store are downloaded locally during the extraction phase. We re-upload files to the Microsoft Dynamics 365 Sales SharePoint document location associated with the parent Account or Opportunity. If the customer does not have SharePoint integration enabled, files attach as notes with file references preserved in Annotation.
Optimiser CRM
Tag/Label
Microsoft Dynamics 365 Sales
Multi-Select Picklist or Topic
lossyTags applied to Contacts or Deals export as label values. We migrate tags as-is into Microsoft Dynamics 365 Sales multi-select picklist fields on Contact and Opportunity. The customer chooses during scoping whether tags map to a dedicated custom multi-select field or to Topics with TopicAssignment records.
| Optimiser CRM | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Pipeline Stage | Stage + Sales Processlossy | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Activity: Call | Task (TaskSubtype = Call)1:1 | Fully supported | |
| Activity: Email | EmailMessage + Task1:1 | Fully supported | |
| Activity: Meeting | Event1:1 | Fully supported | |
| Activity: Note | Annotation1:1 | Fully supported | |
| User/Owner | User1:1 | Fully supported | |
| Document | SharePoint Document or Filelossy | Fully supported | |
| Tag/Label | Multi-Select Picklist or Topiclossy | 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.
Optimiser CRM gotchas
No public API documentation for data export
Custom field schema varies by instance
Automation rules do not transfer
Limited review volume for independent evaluation
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 data export preparation
We audit the Optimiser CRM instance with the customer to enumerate all active objects (Contacts, Companies, Deals, Leads, Activities), custom fields, pipeline stages, and user accounts. Because Optimiser lacks a public API, we identify the CSV export settings, per-run record limits, and date-range or offset pagination strategy needed to extract the full dataset. We request a trial export to enumerate custom field names, validate data completeness, and build the field-level mapping inventory before committing to a migration timeline.
Schema design and Microsoft Dynamics 365 Sales configuration
We design the destination schema in Microsoft Dynamics 365 Sales . This includes creating custom fields to match every active Optimiser custom property, configuring Sales Processes and Record Types to mirror the Optimiser pipeline stages, provisioning the Lead status values, and setting up the Account-Contact relationship model. Schema design is validated in a Microsoft Dynamics 365 Sales sandbox environment before production migration begins. We coordinate with the customer's Microsoft partner or admin to ensure the migration user has the required Dataverse permissions.
Data extraction and CSV pagination
We run the Optimiser CSV export in paginated batches using the strategy defined during discovery. Batches are defined by date range or record ID offset to stay within the per-run record limit. Each batch is downloaded, validated for completeness (row counts, expected column headers), and stored in a staging area before transformation begins. We flag any records modified during the extraction window for a delta re-export before cutover.
Data transformation and field mapping
We transform Optimiser records into Microsoft Dynamics 365 Sales format using the mapping inventory built during discovery. Contacts receive AccountId via domain-match or placeholder Account. Deals map to Opportunities with stage translation. Activities split into Task, Event, and EmailMessage records with parent-record resolution (WhoId, WhatId) against the imported Contacts and Opportunities. Owner resolution maps Optimiser user emails to Dynamics User IDs, with unresolved owners placed in the reconciliation queue.
Sandbox migration and reconciliation
We run a full migration into a Microsoft Dynamics 365 Sales sandbox using production-like data volume. The customer's RevOps lead reviews record counts (Contacts in, Accounts in, Opportunities in, Activities in), spot-checks 25-50 records against the Optimiser source, and validates that stage values, custom field values, and activity timelines match expectations. Any mapping corrections are applied before production migration begins. Owner reconciliation resolves or escalates any remaining unresolved user mappings.
Production migration and cutover
We run production migration in dependency order: Accounts first, then Contacts with AccountId resolved, then Opportunities with AccountId and OwnerId resolved, then Activities via Dataverse API. Each phase emits a row-count reconciliation report before the next phase begins. We freeze Optimiser writes during the cutover window, run a final delta migration of any records modified during migration, and enable Microsoft Dynamics 365 Sales as the system of record. We deliver the automation rebuild checklist mapped to Dynamics Sales accelerator templates and Power Automate. A one-week hypercare window is included for reconciliation issues raised during the first production week.
Platform deep dives
Optimiser CRM
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 6 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Optimiser CRM and Microsoft Dynamics 365 Sales .
Object compatibility
6 of 8 objects need a mapping; the rest are 1:1.
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
Optimiser CRM: Not publicly documented.
Data volume sensitivity
Optimiser 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 Optimiser CRM to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your Optimiser 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 Optimiser 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.