CRM migration

Migrate from CASEpeer to Microsoft Dynamics 365 Sales

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 logo

CASEpeer

Source

Microsoft Dynamics 365 Sales

Destination

Microsoft Dynamics 365 Sales  logo

Compatibility

100%

13 of 13

objects map 1:1 between CASEpeer and Microsoft Dynamics 365 Sales .

Complexity

BStandard

Timeline

72–96 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

CASEpeer logo

CASEpeer

What's pushing teams away

  • Dropbox integration breaks persist without resolution — at least one firm reported a custom folder creation bug lasting five months with no fix, blocking document access for newer client files and forcing workarounds.
  • Texting limitations frustrate communication-heavy workflows — users report lack of mass texting capability, no attachment support in messages, and cluttered in-app notifications that require external tools to replace.
  • Missing features force reliance on external software — essential tasks such as certain document workflows, client intake, and reporting require external actions or third-party integrations that CASEpeer does not natively cover.
  • Document management inconsistencies — folder structures and document naming conventions do not always behave predictably, with one reviewer noting lawyers cannot refer to files that should exist in CASEpeer-hosted folders.
  • Reporting is tier-gated — the Data Sync feature (S3 + Athena + BI tool connectivity) is restricted to the Advanced tier, leaving Basic and Pro users without a native path to operational analytics.

Choosing

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

What's pulling them in

  • Deep Microsoft 365, Teams, and Outlook integration makes Microsoft Dynamics 365 Sales a natural fit for Microsoft-first organizations already invested in that ecosystem
  • Sales Enterprise and Premium tiers offer unlimited custom tables and advanced AI-driven forecasting and predictive analytics not available in lower tiers
  • Professional tier pricing at $65 per user per month offers a lower entry cost than Salesforce for SMB teams with straightforward CRM needs
  • Flexible customization options allow businesses to build bespoke apps, tailor forms and views, and integrate with other Dynamics 365 modules
  • Microsoft Copilot AI tools are embedded directly into the sales workflow on Enterprise and Premium, automating routine tasks and providing deal intelligence

Object mapping

How CASEpeer objects map to Microsoft Dynamics 365 Sales

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

maps to

Microsoft Dynamics 365 Sales

Opportunity

1:1
Fully supported

CASEpeer 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

maps to

Microsoft Dynamics 365 Sales

Opportunity Stage

1:1
Fully supported

CASEpeer 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

maps to

Microsoft Dynamics 365 Sales

Contact

1:1
Fully supported

CASEpeer 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

maps to

Microsoft Dynamics 365 Sales

Contact

1:1
Fully supported

Opposing 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

maps to

Microsoft Dynamics 365 Sales

Account

1:1
Fully supported

CASEpeer 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

maps to

Microsoft Dynamics 365 Sales

Contact

1:1
Fully supported

Medical 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

maps to

Microsoft Dynamics 365 Sales

Task

1:1
Fully supported

CASEpeer 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

maps to

Microsoft Dynamics 365 Sales

Appointment

1:1
Fully supported

CASEpeer 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

maps to

Microsoft Dynamics 365 Sales

SharePoint Location / Note

1:1
Fully supported

CASEpeer 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

maps to

Microsoft Dynamics 365 Sales

Custom Columns

1:1
Fully supported

CASEpeer 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

maps to

Microsoft Dynamics 365 Sales

Owner (User)

1:1
Fully supported

CASEpeer 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

maps to

Microsoft Dynamics 365 Sales

Custom Column on Opportunity

1:1
Fully supported

Settlement 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

maps to

Microsoft Dynamics 365 Sales

Custom Column on Opportunity

1:1
Fully supported

CASEpeer 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.

Gotchas + challenges

What specifically takes care here

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 logo

CASEpeer gotchas

High

Dropbox custom folder creation fails silently for extended periods

Medium

Custom fields unavailable on the Client Intake Form

Medium

Data Sync is a daily batch export, not a live data feed

Low

Mass texting and attachment-in-text unavailable across all tiers

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales gotchas

High

Professional tier 15-table custom table limit blocks migrations

High

October 2024 pricing increase applies at renewal for all customers

Medium

Custom fields must be created in the UI before API writes

Medium

Power Platform request limits apply to bulk migrations

Medium

Activity records orphaned to inactive owners fail silently

Pair-specific challenges

  • Sales Professional's 5-table limit constrains CASEpeer custom intake field migration

    Dynamics 365 Sales Professional caps custom tables at 5. CASEpeer firms using Advanced tier with multiple case types (auto, medical malpractice, slip-and-fall) may have more than 5 distinct intake-form field groups. Each group requires its own custom table or custom columns on Opportunity. We audit the CASEpeer schema during the pre-migration discovery and flag whether Enterprise licensing is required before data lands. This is not a migration blocker—it is a licensing decision that must be made before the migration run.

  • CASEpeer case-to-contact relationship is N:1 while Dynamics 365 Opportunity-to-Contact uses a junction model

    A single CASEpeer case can have multiple plaintiffs, multiple opposing parties, multiple medical providers, and multiple insurers—each stored as separate relationship records. Dynamics 365 Opportunity uses the Opportunity Contact Role table (built-in junction) for the primary plaintiff contact and can link additional contacts via the same table. We map every CASEpeer contact-case relationship to Opportunity Contact Roles in Dynamics 365, preserving the contact's role value (Plaintiff, Opposing Party, Medical Provider) so nothing collapses into a single primary contact during the migration.

  • Statute of limitations tracking requires a custom date field in Dynamics 365

    CASEpeer includes statute of limitations (SOL) date tracking as a core field on cases. Dynamics 365 Opportunity has no native SOL field—litigation-focused firms must create a custom date column (Sol_Date__c) on the Opportunity table. We add this column during schema setup and map the CASEpeer value. However, Dynamics 365 does not natively alert users to approaching SOL dates; firms need a Power Automate flow or business rule to generate reminders, which is outside the data-migration scope.

  • CASEpeer Dropbox file sync issues do not transfer—document migration requires SharePoint setup

    CASEpeer review themes report persistent Dropbox folder creation failures where new client files cannot attach to the correct folder. This is a CASEpeer integration issue, not a data problem. The actual documents attached to CASEpeer case records migrate to Dynamics 365 SharePoint integration (if enabled) or as Note records attached to the Opportunity. Firms must configure the Dynamics 365 SharePoint integration in their tenant before migration—we flag this as a prerequisite and do not attempt document migration without it.

  • Insurance carrier as Account requires pre-migration Account deduplication

    CASEpeer stores insurance carriers as free-text references on the case. Dynamics 365 maps carriers to Accounts. Multiple CASEpeer cases referencing the same carrier (e.g., 'State Farm') may arrive as duplicate Account records if carrier names are spelled inconsistently (e.g., 'State Farm Ins.', 'State Farm Mutual'). We deduplicate carrier names by normalized match before creating Account records, but firms with dozens of carrier variations should review the carrier list in CASEpeer before migration.

Migration approach

Six steps for a successful CASEpeer to Microsoft Dynamics 365 Sales data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

CASEpeer logo

CASEpeer

Source

Strengths

  • Purpose-built for personal injury — case stages, medical treatment tracking, and settlement workflows reflect deep domain knowledge.
  • Per-user monthly pricing is transparent and predictable across all three tiers.
  • Firm-assisted onboarding data transfer process reduces risk during initial setup.
  • Texting is native with permission controls and scheduling, reducing reliance on separate communication tools.
  • Legal-specific integrations with LawPay, CalendarRules, and Records On Time are available out of the box.

Weaknesses

  • Dropbox custom folder creation has a documented bug persisting months without resolution.
  • Text messaging lacks mass texting and attachment support, limiting communication workflow depth.
  • Custom fields are restricted to intake forms and cannot be added to the base Client Intake Form.
  • Document management is inconsistent, with folder and file behavior varying unpredictably.
  • Reporting and analytics require the top-tier Advanced plan and additional BI tooling.
Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

Destination

Strengths

  • Native integration with Microsoft 365, Teams, Outlook, and SharePoint for unified productivity workflow
  • Unlimited custom tables and complex workflows on Enterprise tier enable deep customization for complex sales processes
  • AI-driven predictive analytics and deal intelligence on Enterprise and Premium tiers help sales teams prioritize pipeline
  • Dataverse unified data layer provides a consistent API and data model across all Dynamics 365 and Power Platform apps
  • Strong security model with Field-Level Security and Record Ownership rules for governance-conscious enterprises

Weaknesses

  • Sales Professional tier caps custom tables at 15, creating a migration ceiling for highly customized SMB environments
  • October 2024 pricing increases of $15 per user across all tiers apply to existing customers upon renewal
  • Implementation typically requires costly certified partners, adding 30–50% to total project cost
  • Updates and platform releases can disrupt customizations and plugins, requiring regression testing after each wave
  • Non-Microsoft integrations require additional configuration or middleware, limiting flexibility for heterogeneous tech stacks

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across CASEpeer and Microsoft Dynamics 365 Sales .

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    CASEpeer: Not publicly documented — CASEpeer does not publish a general developer portal with limits. Partner integrations operate under contractually defined thresholds..

  • Data volume sensitivity

    B

    CASEpeer doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your CASEpeer to Microsoft Dynamics 365 Sales migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about CASEpeer to Microsoft Dynamics 365 Sales data migrations

Answers to the questions buyers ask most during CASEpeer to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most CASEpeer to Dynamics 365 migrations complete within 72–96 hours for firms with fewer than 25,000 records. Firms with over 200,000 records, multiple case types, and extensive custom intake fields extend to 10–15 days. The licensing assessment and custom column creation add 3–5 days of pre-migration prep. The delta-pickup window runs 24–48 hours post-cutover. Dynamics 365 SharePoint integration setup, if not already enabled, is a separate admin task that must complete before document migration begins.

Adjacent paths

Related migrations to explore

Ready when you are

Move from CASEpeer.
Land in Microsoft Dynamics 365 Sales , intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day