CRM migration

Migrate from SimplyConvert to Microsoft Dynamics 365 Sales

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 logo

SimplyConvert

Source

Microsoft Dynamics 365 Sales

Destination

Microsoft Dynamics 365 Sales  logo

Compatibility

90%

9 of 10

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

Complexity

BStandard

Timeline

24–48 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

SimplyConvert logo

SimplyConvert

What's pushing teams away

  • Per-conversion pricing model creates unpredictable and escalating costs as claimant volume grows in active litigations
  • Narrow focus on mass tort intake makes the platform unsuitable for firms with diverse practice areas requiring broader case management
  • Small vendor footprint with 23 employees and ~$1M revenue raises long-term support and platform stability concerns
  • Limited third-party integrations beyond native API constrains how SimplyConvert data connects to downstream accounting, e-billing, or e-discovery tools
  • Custom reporting insufficient for firms managing multiple simultaneous litigations needing cross-case analytics and settlement benchmarking

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 SimplyConvert objects map to Microsoft Dynamics 365 Sales

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)

maps to

Microsoft Dynamics 365 Sales

Contact

1:1
Fully supported

SimplyConvert 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)

maps to

Microsoft Dynamics 365 Sales

Lead

1:many
Fully supported

SimplyConvert 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)

maps to

Microsoft Dynamics 365 Sales

Account

1:1
Fully supported

SimplyConvert 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)

maps to

Microsoft Dynamics 365 Sales

Opportunity

1:1
Fully supported

SimplyConvert 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)

maps to

Microsoft Dynamics 365 Sales

Lead

1:1
Fully supported

SimplyConvert 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)

maps to

Microsoft Dynamics 365 Sales

Opportunity (Closed)

1:1
Fully supported

SimplyConvert 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)

maps to

Microsoft Dynamics 365 Sales

Task / Appointment / PhoneCall / Email

1:1
Fully supported

SimplyConvert 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

maps to

Microsoft Dynamics 365 Sales

SharePoint / Note (Annotation)

1:1
Fully supported

SimplyConvert 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

maps to

Microsoft Dynamics 365 Sales

SystemUser

1:1
Fully supported

SimplyConvert 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

maps to

Microsoft Dynamics 365 Sales

Custom Fields (Custom Columns in Dataverse)

1:1
Fully supported

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

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.

SimplyConvert logo

SimplyConvert gotchas

High

Per-conversion billing requires conversion-status audit before migration

High

No bulk export endpoint forces pagination under strict rate limits

Medium

No standalone Contact object requires structural flattening

Medium

API key generation requires direct vendor contact

Low

Named litigation groupings not exposed as filterable objects

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

  • Case-to-opportunity stage mapping requires a value table per Dynamics 365 Sales Process

    SimplyConvert case stages (New, Screening, Accepted, Closed) do not map directly to Dynamics 365 Opportunity stages, which are scoped by Sales Process. A single Dynamics 365 organization may have multiple Sales Processes (e.g., 'Personal Injury Pipeline', 'Mass Tort Pipeline') each with different stage names and probabilities. We build a value-mapping table for each Sales Process before migration, applying the correct StageName per case type. Without this pre-work, all cases land in the default pipeline with mismatched stage labels.

  • SimplyConvert's multi-firm contact associations collapse to a single AccountId in Dynamics 365

    SimplyConvert allows a single contact to be associated with multiple law firms simultaneously (e.g., a referring attorney who works across firms). Dynamics 365 Contacts have a single primary AccountId; additional firm relationships use the Account Contact Role entity. We migrate the most-recently-modified firm association as the primary AccountId and surface remaining firm links as Account Contact Roles. Firms should review whether all firm associations are critical for Dynamics 365 reporting before migration runs.

  • Sales Professional edition limits custom tables to 15, which may not cover all legal-case custom fields

    SimplyConvert custom intake properties (injury type, statute of limitations, jurisdiction, opposing counsel, medical provider) multiply quickly for mass-tort practices. Dynamics 365 Sales Professional caps custom tables at 15. Firms with more than 15 distinct custom properties need Sales Enterprise licensing to accommodate all fields on the Opportunity table, or we consolidate related properties into JSON-encoded text fields or option-set pick-lists. We flag this before migration scoping so licensing decisions are made early.

  • SimplyConvert intake workflows and referral routing rules have no Dynamics 365 equivalent

    SimplyConvert automations that route incoming leads to staff based on case type, jurisdiction, or intake criteria are built within the SimplyConvert platform and do not export. These automations must be rebuilt using Dynamics 365 Power Automate flows, Business Process Flows, or Dataverse workflows post-migration. We export SimplyConvert workflow definitions as a configuration reference document for the Dynamics 365 admin to use during the rebuild phase. The exported document includes trigger conditions, action steps, and field mappings so administrators can replicate routing logic in Power Automate cloud flows or Dataverse workflow steps. Planning for this rebuild before go-live prevents gaps in lead handling and ensures continuity of case intake processes.

Migration approach

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

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

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

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

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

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

Context on both ends of the pair

SimplyConvert logo

SimplyConvert

Source

Strengths

  • Purpose-built for mass tort claimant intake with chatbot, TDP scoring, and claim form population in a single workflow
  • ABA-recognized legal tech innovator with lawyer-founded development team understands litigation-specific data requirements
  • Integrated referral platform and CaseHQ client portal consolidate intake and client-facing communication
  • Real-time case notifications and lead ranking directly support settlement-focused case management priorities
  • Per-conversion pricing aligns cost with firm revenue for high-volume litigations with clear intake-to-contract conversion

Weaknesses

  • Pay-per-conversion billing creates unpredictable and escalating costs as claimant volume grows across active litigations
  • Narrow mass tort specialization unsuitable for firms managing diverse practice areas beyond claimant intake
  • Small vendor footprint (23 employees, ~$1M revenue) raises long-term stability and support-capacity concerns
  • No dedicated bulk export API; large case histories require pagination through the 300 req/min List Cases endpoint
  • Limited documented API coverage for non-Case objects including Contacts, Users, and custom objects
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. All 8 core objects map 1:1 between SimplyConvert and Microsoft Dynamics 365 Sales .

B

Overall complexity

Standard migration

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

  • Object compatibility

    A

    All 8 core objects map 1:1 between SimplyConvert and Microsoft Dynamics 365 Sales .

  • 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

    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

    B

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

Estimator

Estimate your SimplyConvert 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 SimplyConvert to Microsoft Dynamics 365 Sales data migrations

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

Can't find your answer?

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 consultation

Most SimplyConvert-to-Dynamics 365 migrations complete in 24–48 hours for migrations under 10,000 records. Larger firms with 10,000+ records, extensive custom intake properties, or multi-firm contact associations extend to 7–14 days. The longest planning step is mapping SimplyConvert case stages to Dynamics 365 Sales Processes and building the custom field schema for legal-specific properties. The migration itself runs against SimplyConvert's API within its rate limits, and the delta-pickup window adds 24–48 hours to capture cutover changes.

Adjacent paths

Related migrations to explore

Ready when you are

Move from SimplyConvert.
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