CRM migration
Field-level mapping, validation, and rollback between SimplyConvert and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
SimplyConvert
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
9 of 10
objects map 1:1 between SimplyConvert and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
24–48 hours
Overview
SimplyConvert serves law firms handling mass tort and personal injury claims, organizing data around client intake cases, referred contacts, and firm relationships. Dynamics 365 Sales uses the standard Microsoft CRM data model with Accounts, Contacts, Leads, and Opportunities as core entities. The migration maps SimplyConvert's intake-oriented structure onto Dynamics 365's sales-pipeline model: SimplyConvert contacts and firms become Dynamics 365 Contacts and Accounts, while active legal cases requiring ongoing representation map to Opportunities with custom fields for case-specific attributes. Document attachments re-upload to Dynamics 365's SharePoint-backed file storage. FlitStack AI sequences the migration so foreign-key relationships resolve correctly — Accounts before Contacts, Contacts before Opportunities — and uses a 24–48 hour delta-pickup window to capture any records modified during cutover. Automation logic (SimplyConvert intake workflows, referral routing rules) does not migrate and must be rebuilt in Dynamics 365 using Power Automate flows or Dataverse workflows. The API-based migration respects SimplyConvert's rate limits (300 requests per minute for list operations, 2,000 per minute for individual record operations) and logs every operation in an audit trail.
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
SimplyConvert platform overview
Scorecard, SWOT, gotchas, and pricing for SimplyConvert.
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 SimplyConvert 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.
SimplyConvert
Contact (Client/Prospect)
Microsoft Dynamics 365 Sales
Contact
1:1SimplyConvert contacts map to Dynamics 365 Contacts. Each contact requires a primary AccountId — if the contact has no associated firm in SimplyConvert, we attach to a default 'Individual' Account or create one. Contact type (Client vs. Prospect) maps to a custom Contact_Type__c pick-list field.
SimplyConvert
Contact (Referral Source)
Microsoft Dynamics 365 Sales
Lead
1:manySimplyConvert contacts tagged as referral sources (attorneys, referring firms) route to Dynamics 365 Leads. The referral source type maps to Lead Source pick-list values. If the referral contact already has a signed matter in SimplyConvert, that contact also migrates as a Contact linked to the Account.
SimplyConvert
Company (Law Firm/Referring Firm)
Microsoft Dynamics 365 Sales
Account
1:1SimplyConvert firm records map to Dynamics 365 Accounts. Firm name maps to Account.Name, website to Website, phone to Telephone, and industry to Industry (pre-populated as 'Legal Services'). Parent-child firm hierarchies in SimplyConvert map to Account.ParentAccountId. Address components (street, city, state, zip) map to Account.Address1 fields, and any custom firm classification (e.g., 'Plaintiff Firm') populates a custom Account_Type__c field for segmentation.
SimplyConvert
Case (Intake Matter)
Microsoft Dynamics 365 Sales
Opportunity
1:1SimplyConvert cases with status 'Accepted' or 'Active' map to Dynamics 365 Opportunities representing active legal matters. The case name becomes Opportunity.Name, case amount maps to Amount, and case stage maps to StageName via a value-mapping table. Each Opportunity links to the primary Contact (plaintiff) and the Account (defendant or opposing party if applicable).
SimplyConvert
Case (Pre-Acceptance)
Microsoft Dynamics 365 Sales
Lead
1:1SimplyConvert cases with status 'New', 'Screening', or 'Under Review' map to Dynamics 365 Leads. The case details migrate as Lead custom fields. When the case advances in SimplyConvert, the Lead converts to an Opportunity in Dynamics 365. Including case type, incident date, and jurisdiction, ensuring continuity of case context in the lead record.
SimplyConvert
Case (Resolved/Closed)
Microsoft Dynamics 365 Sales
Opportunity (Closed)
1:1SimplyConvert cases with status 'Closed-Won' or 'Closed-Lost' migrate as closed Dynamics 365 Opportunities with StageName = 'Closed Won' or 'Closed Lost'. Settlement amount maps to Amount, and closedate is set from the case close date in SimplyConvert. The close reason field captures the outcome type, and any final notes are preserved in the closed Opportunity's description.
SimplyConvert
Activity (Call, Email, Meeting, Note)
Microsoft Dynamics 365 Sales
Task / Appointment / PhoneCall / Email
1:1SimplyConvert activity records map by type: calls to PhoneCall, emails to Email (or Task with 'Email' activity type), meetings to Appointment, and notes to Note. Original timestamps, subject, and body text are preserved. The activity links to the parent Contact or Case (Opportunity) record.
SimplyConvert
Document / Attachment
Microsoft Dynamics 365 Sales
SharePoint / Note (Annotation)
1:1SimplyConvert documents are downloaded and re-uploaded to Dynamics 365 SharePoint document locations keyed by entity (Contact, Account, Opportunity). Documents attached to cases land in the Opportunity's SharePoint folder. File size limits (default 10MB per file in SharePoint Online) are enforced during migration.
SimplyConvert
User / Owner
Microsoft Dynamics 365 Sales
SystemUser
1:1SimplyConvert owner_id resolves to a Dynamics 365 SystemUser by email match. Unmatched owners are flagged in the pre-migration report — firms either invite them to Dynamics 365 first or assign their records to a designated fallback owner before migration runs.
SimplyConvert
Custom Properties
Microsoft Dynamics 365 Sales
Custom Fields (Custom Columns in Dataverse)
1:1SimplyConvert custom intake properties (injury type, statute of limitations, jurisdiction, opposing counsel) migrate as custom columns on the Contact or Opportunity table in Dynamics 365. Field type is preserved: text fields become Text, dates become DateTime, pick-lists become Choice columns. Custom property count drives the upper pricing tier.
| SimplyConvert | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Contact (Client/Prospect) | Contact1:1 | Fully supported | |
| Contact (Referral Source) | Lead1:many | Fully supported | |
| Company (Law Firm/Referring Firm) | Account1:1 | Fully supported | |
| Case (Intake Matter) | Opportunity1:1 | Fully supported | |
| Case (Pre-Acceptance) | Lead1:1 | Fully supported | |
| Case (Resolved/Closed) | Opportunity (Closed)1:1 | Fully supported | |
| Activity (Call, Email, Meeting, Note) | Task / Appointment / PhoneCall / Email1:1 | Fully supported | |
| Document / Attachment | SharePoint / Note (Annotation)1:1 | Fully supported | |
| User / Owner | SystemUser1:1 | Fully supported | |
| Custom Properties | Custom Fields (Custom Columns in Dataverse)1: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.
SimplyConvert gotchas
Per-conversion billing requires conversion-status audit before migration
No bulk export endpoint forces pagination under strict rate limits
No standalone Contact object requires structural flattening
API key generation requires direct vendor contact
Named litigation groupings not exposed as filterable objects
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
Audit SimplyConvert data model and map custom properties to Dynamics 365 custom fields
FlitStack AI exports the full SimplyConvert schema — standard and custom fields across contacts, firms, cases, and activities — and cross-references it against Dynamics 365's standard schema. We identify custom properties that require new custom columns in Dynamics 365, flag pick-list value mappings needed for case stages and contact types, and deliver a schema setup plan. If your Dynamics 365 license is Sales Professional, we verify that the custom property count fits within the 15-table limit or recommend an upgrade path before migration begins.
Resolve SimplyConvert owners to Dynamics 365 SystemUser records by email
Each SimplyConvert owner_id is matched against Dynamics 365 users by email address. Any SimplyConvert owner who does not have a corresponding Dynamics 365 user account is flagged in a pre-migration report with the owner's name and email. Your team either creates the SystemUser record in Dynamics 365 before migration or designates a fallback owner to assign those records to. No record migrates without a resolved OwnerId.
Sequence migration: Accounts → Contacts → Opportunities → Activities → Documents
Dynamics 365 enforces referential integrity — Accounts must exist before Contacts (via AccountId lookup), and Contacts should exist before Opportunities (for Opportunity Contact Roles). We sequence the migration to resolve foreign keys in the correct order: law firms to Accounts, clients to Contacts (with AccountId set), active intake cases to Opportunities (linked to Contact and Account), activities to their parent records, and documents to SharePoint locations. This ordering prevents orphaned records and duplicate inserts.
Run sample migration with field-level diff across representative case types
A representative slice of records — spanning contacts from different case types, firms with varying firm-type classifications, active and closed cases, and a sample of activities and documents — migrates first. We generate a field-level diff report comparing each source field value against the destination field value so you can verify case-stage mapping, custom property placement, owner resolution, and document link integrity before the full run commits. Any mapping errors are corrected in the migration plan and the sample re-run.
Execute full migration with delta-pickup window and audit logging
The full migration runs against Dynamics 365 using the validated mapping. A delta-pickup window of 24–48 hours opens simultaneously, capturing any records created or modified in SimplyConvert during the cutover window so Dynamics 365 reflects the final source state at go-live. FlitStack AI logs every insert, update, and skip operation in an audit log. If reconciliation fails or record counts are outside acceptable variance thresholds, one-click rollback reverts the Dynamics 365 environment to its pre-migration state.
Platform deep dives
SimplyConvert
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between SimplyConvert and Microsoft Dynamics 365 Sales .
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across SimplyConvert and Microsoft Dynamics 365 Sales .
Object compatibility
All 8 core objects map 1:1 between SimplyConvert 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
SimplyConvert: 300 req/min for List Cases; 2000 req/min for Get Case and Create Case; 200 req/min for Upload Documents and Download Documents; 2000 req/min for all unspecified endpoints.
Data volume sensitivity
SimplyConvert 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 SimplyConvert to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your SimplyConvert 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 SimplyConvert
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.