CRM migration
Field-level mapping, validation, and rollback between CASEpeer and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
CASEpeer
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
13 of 13
objects map 1:1 between CASEpeer and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
72–96 hours
Overview
CASEpeer organizes personal injury practice data around cases, clients, opposing parties, medical records, and case-stage workflows. Dynamics 365 Sales (built on Dataverse) uses Leads, Accounts, Contacts, and Opportunities as its core tables, with custom tables available on Enterprise tier. The migration maps CASEpeer Cases to Opportunities where the matter represents a revenue-generating event, CASEpeer Clients to Contacts with a custom Role field distinguishing plaintiff from opposing party, and CASEpeer's custom intake fields to Dynamics 365 custom columns on the appropriate table. CASEpeer attorney-assignment and staff-owner data resolves by email match against Dynamics 365 users. Case-stage history, settlement amounts, and insurance claim values migrate as custom fields on the Opportunity record. Workflows, automation rules, and custom intake form logic in CASEpeer do not transfer—they must be rebuilt in Dynamics 365 using Power Automate or the business rules engine. FlitStack AI sequences the migration using Dynamics 365's Table dependencies: Accounts first, then Contacts, then Opportunities with the Account lookup resolved before Contacts land.
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
CASEpeer platform overview
Scorecard, SWOT, gotchas, and pricing for CASEpeer.
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 CASEpeer 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.
CASEpeer
Case
Microsoft Dynamics 365 Sales
Opportunity
1:1CASEpeer Cases map to Dynamics 365 Opportunities. Each CASEpeer case with an estimated settlement or contingency fee becomes an Opportunity with Amount set to the estimated case value. Case number migrates as a custom field for traceability. The mapping preserves the original case open date as the Opportunity CreatedOn timestamp, ensuring a complete historical record from intake onward.
CASEpeer
Case Stage
Microsoft Dynamics 365 Sales
Opportunity Stage
1:1CASEpeer stage values (Intake, Investigation, Litigation, Settlement, Trial, Closed) map to Dynamics 365 Opportunity Stage values. Custom stages require value-by-value mapping; probability weights re-applied on the Dynamics 365 side per business process. The stage mapping also includes a custom field for stage entry date, enabling historical stage duration analysis in Power BI.
CASEpeer
Client / Plaintiff
Microsoft Dynamics 365 Sales
Contact
1:1CASEpeer clients map to Dynamics 365 Contacts. The Contact's Role__c custom column (value: 'Plaintiff' or 'Client') distinguishes them from opposing parties. Primary phone, email, and address fields migrate directly. The mapping also preserves the original client create date as the Contact's CreatedOn timestamp, maintaining the full client history.
CASEpeer
Opposing Party / Defendant
Microsoft Dynamics 365 Sales
Contact
1:1Opposing parties in CASEpeer become Dynamics 365 Contacts with Role__c set to 'Opposing Party'. Contact's AccountId links to the opposing party's organization record where applicable. The mapping also captures the opposing party's address and phone details, storing them in the Contact's standard address fields for straightforward retrieval.
CASEpeer
Insurance Carrier
Microsoft Dynamics 365 Sales
Account
1:1CASEpeer insurance carrier references map to Dynamics 365 Accounts representing the insurer. Carrier name, policy number, and coverage limits migrate as custom columns on the Account record. The mapping also stores the carrier's contact name and phone as a secondary contact on the Account, enabling direct communication for claim updates.
CASEpeer
Medical Provider
Microsoft Dynamics 365 Sales
Contact
1:1Medical providers linked to a CASEpeer case become Dynamics 365 Contacts with Role__c set to 'Medical Provider'. Provider's facility name migrates as Account.Name with the Contact linked via AccountId. The mapping also captures the provider's specialty and office phone as custom fields on the Contact, supporting referral tracking and communication.
CASEpeer
Case Task
Microsoft Dynamics 365 Sales
Task
1:1CASEpeer tasks attached to cases migrate as Dynamics 365 Tasks with RegardingObjectId pointing to the corresponding Opportunity record. Original due dates, priorities, and assigned users (resolved by email) are preserved. The mapping also retains the task's original description and any attached notes, ensuring complete activity history for audit purposes.
CASEpeer
Calendar Event
Microsoft Dynamics 365 Sales
Appointment
1:1CASEpeer calendar events become Dynamics 365 Appointments with RegardingObjectId linked to the relevant Opportunity. Original start/end times, location, and attendees (resolved by email) are carried forward. The mapping also preserves the appointment's subject line and any notes, providing a full timeline of case-related meetings for reporting.
CASEpeer
Document / Attachment
Microsoft Dynamics 365 Sales
SharePoint Location / Note
1:1CASEpeer document attachments re-upload to Dynamics 365 SharePoint integration or Note records attached to the Opportunity. File size limits apply (default 10MB per file in Dataverse). Firms must enable SharePoint integration in Dynamics 365 before migration. During re-upload, folder structures are recreated to match the original CASEpeer case hierarchy, preserving logical organization.
CASEpeer
Custom Intake Fields
Microsoft Dynamics 365 Sales
Custom Columns
1:1CASEpeer custom intake form fields per case type map to Dynamics 365 custom columns on the Opportunity table. Data types (text, number, date, picklist) are preserved. Sales Professional's 5-table limit may require Enterprise licensing for firms with more than 5 case-type field groups.
CASEpeer
Staff / Attorney Assignment
Microsoft Dynamics 365 Sales
Owner (User)
1:1CASEpeer attorney and staff assignments resolve by email match against Dynamics 365 users. Unmatched staff are flagged before migration; records assign to a fallback owner. CASEpeer role types (Partner, Associate, Paralegal) migrate as a custom column. The resolution process also captures the user's department and manager, enabling reporting on case workload distribution across the firm.
CASEpeer
Settlement Amount
Microsoft Dynamics 365 Sales
Custom Column on Opportunity
1:1Settlement values and contingency fee percentages in CASEpeer migrate as custom columns (Settlement_Amount__c, Contingency_Fee_Pct__c) on the Opportunity. Closed-won Opportunities hold actual settlement amounts; open cases hold estimated values. These columns are formatted as currency fields, enabling straightforward financial analysis and reporting in Power BI dashboards.
CASEpeer
Insurance Claim Number
Microsoft Dynamics 365 Sales
Custom Column on Opportunity
1:1CASEpeer insurance claim references migrate as a custom text column on the Opportunity record. Claims adjuster contact info, where present, attaches as a separate Contact with Role__c set to 'Adjuster'. The adjuster's phone and email are stored in the Contact's standard phone and email fields, facilitating direct communication during claim processing.
| CASEpeer | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Case | Opportunity1:1 | Fully supported | |
| Case Stage | Opportunity Stage1:1 | Fully supported | |
| Client / Plaintiff | Contact1:1 | Fully supported | |
| Opposing Party / Defendant | Contact1:1 | Fully supported | |
| Insurance Carrier | Account1:1 | Fully supported | |
| Medical Provider | Contact1:1 | Fully supported | |
| Case Task | Task1:1 | Fully supported | |
| Calendar Event | Appointment1:1 | Fully supported | |
| Document / Attachment | SharePoint Location / Note1:1 | Fully supported | |
| Custom Intake Fields | Custom Columns1:1 | Fully supported | |
| Staff / Attorney Assignment | Owner (User)1:1 | Fully supported | |
| Settlement Amount | Custom Column on Opportunity1:1 | Fully supported | |
| Insurance Claim Number | Custom Column on Opportunity1: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.
CASEpeer gotchas
Dropbox custom folder creation fails silently for extended periods
Custom fields unavailable on the Client Intake Form
Data Sync is a daily batch export, not a live data feed
Mass texting and attachment-in-text unavailable across all tiers
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 CASEpeer schema and Dynamics 365 licensing assessment
FlitStack AI extracts the full CASEpeer object list including custom intake field names, data types, and case-type associations. We count unique contact roles, carrier names, and custom fields per case type to assess Dynamics 365 table and column requirements. If custom field groups exceed the Sales Professional 5-table limit, we document the Enterprise licensing requirement and confirm before proceeding. The audit generates a schema report that identifies any missing Dynamics 365 tables and flags the need for custom column creation prior to data load.
Create Dynamics 365 custom columns and configure SharePoint integration
We create all required custom columns on the Opportunity, Contact, and Account tables (Sol_Date__c, Settlement_Amount__c, Contingency_Fee_Pct__c, Case_Type__c, Role__c, etc.) via the Dynamics 365 solution layer. If SharePoint integration is not yet configured, we document the Microsoft 365 admin steps required to enable document management and confirm readiness before document migration begins. These columns include date, currency, and picklist types to capture case-specific data such as statute of limitations, settlement amounts, and case type classification.
Resolve attorneys and staff by email against Dynamics 365 users
CASEpeer attorney and staff assignments extract as owner references. We run an email-matching job against the Dynamics 365 user list. Unmatched users are flagged in a pre-migration report—firms either invite them to Dynamics 365 before migration or assign their records to a designated fallback user. No record lands in Dynamics 365 without a valid OwnerId. The matching process uses the UserPrincipalName (UPN) to ensure accurate alignment, and any remaining gaps are resolved before the final migration run to avoid orphaned records.
Migrate Accounts, Contacts, and Opportunities in dependency order
Dynamics 365 requires AccountId on Contact and Opportunity Contact Roles before Opportunities can link contacts. We sequence the migration: Accounts first (carriers, opposing party organizations), then Contacts (plaintiffs, opposing parties, medical providers, adjusters), then Opportunities with AccountId resolved and Opportunity Contact Roles established for every linked contact. CASEpeer case-stage history migrates as a custom text audit trail on each Opportunity.
Run sample migration with field-level diff and delta-pickup window
A representative slice of 100–300 records (spanning multiple case types, contact roles, and staff assignments) migrates first. We generate a field-level diff between the CASEpeer source values and the Dynamics 365 destination values so you can verify stage mapping, contact role assignment, and attorney resolution before the full run commits. After full migration, a delta-pickup window (24–48 hours) captures any CASEpeer records modified during the cutover period.
Platform deep dives
CASEpeer
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across CASEpeer and Microsoft Dynamics 365 Sales .
Object compatibility
1 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
CASEpeer: Not publicly documented — CASEpeer does not publish a general developer portal with limits. Partner integrations operate under contractually defined thresholds..
Data volume sensitivity
CASEpeer 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 CASEpeer to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your CASEpeer 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 CASEpeer
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.