CRM migration

Migrate from The Attorney Case File to Microsoft Dynamics 365 Sales

Field-level mapping, validation, and rollback between The Attorney Case File and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .

The Attorney Case File logo

The Attorney Case File

Source

Microsoft Dynamics 365 Sales

Destination

Microsoft Dynamics 365 Sales  logo

Compatibility

100%

10 of 10

objects map 1:1 between The Attorney Case File and Microsoft Dynamics 365 Sales .

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

The Attorney Case File organizes legal work around matters and clients, storing documents, time entries, and billing records within a case-centric model. Dynamics 365 Sales uses a lead-to-opportunity pipeline architecture built on Dataverse, where accounts and contacts drive the sales process with configurable business processes and opportunity stages. The migration translates The Attorney Case File's matter records into Dynamics 365 accounts (for clients) and custom tables (for legal matters), while time entries and billing data surface as notes, custom decimal fields, or related opportunity records depending on your billing workflow. We preserve attorney and staff assignments by resolving source owner emails to Dynamics 365 users, flagging any unmatched owners before migration commits. Workflows, document templates, and merge-field configurations do not migrate — those require Dynamics 365 Power Automate flows and SharePoint document library setup post-migration. The migration runs via Dynamics 365 Web API and Dataverse bulk operations, with a 24–48 hour delta pickup capturing any matter changes during the cutover window.

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

The Attorney Case File logo

The Attorney Case File

What's pushing teams away

  • Users handling multi-party or high-complexity litigation report the system reaches its limits and lacks the structural depth required for matters with numerous interrelated parties and documents.
  • The document management component draws consistent criticism for being underpowered — attorneys working with large document volumes find it inadequate for their needs.
  • At least one review flags platform stability concerns and lack of clear development roadmap, leaving practitioners uncertain about long-term viability and feature evolution.

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 The Attorney Case File objects map to Microsoft Dynamics 365 Sales

Each row shows how a The Attorney Case File 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.

The Attorney Case File

Matter (Client Matter)

maps to

Microsoft Dynamics 365 Sales

Account

1:1
Fully supported

The Attorney Case File matter record (representing a client or case) becomes a Dynamics 365 Account. The matter name maps to Account.Name, and the primary client contact becomes the primary Contact lookup on the Account. Matter status (Active, Closed, Pending) maps to a custom pick-list field on the Account.

The Attorney Case File

Client Contact

maps to

Microsoft Dynamics 365 Sales

Contact

1:1
Fully supported

Client contacts from The Attorney Case File map directly to Dynamics 365 Contact records. Each contact is linked to its parent Account via the Account Lookup field. Contact roles (Primary Attorney, Referring Attorney, Client) are preserved as a custom pick-list field on the Contact or as Account Contact Relationships.

The Attorney Case File

Attorney / Staff User

maps to

Microsoft Dynamics 365 Sales

SystemUser (Dynamics 365 User)

1:1
Fully supported

The Attorney Case File attorney and staff records map to Dynamics 365 SystemUser entities. Matching occurs by email address — FlitStack AI resolves each source owner email to the corresponding Dynamics 365 user ID. Unmatched owners are flagged before migration so your admin can provision accounts first.

The Attorney Case File

Time Entry

maps to

Microsoft Dynamics 365 Sales

Custom Table: TimeEntry

1:1
Fully supported

Time entries from The Attorney Case File (date, hours, attorney, matter, billing rate, description) do not have a native Dynamics 365 equivalent. We create a custom Dataverse table (attorneycasefile_timeentry) with columns for EntryDate, Hours, Rate, BilledAmount, Attorney (User lookup), and Matter (Account lookup), preserving original timestamps and attorney attribution.

The Attorney Case File

Invoice / Bill

maps to

Microsoft Dynamics 365 Sales

Custom Table: Invoice

1:1
Fully supported

Invoices from The Attorney Case File map to a custom Dataverse invoice table. Fields include InvoiceNumber, InvoiceDate, TotalAmount, BalanceDue, Status, Matter (Account lookup), and line items as a related custom table. Dynamics 365 Finance modules handle full billing natively — this migration delivers data only, not a billing workflow.

The Attorney Case File

Document Reference

maps to

Microsoft Dynamics 365 Sales

SharePointDocumentLocation + Note

1:1
Fully supported

Documents attached in The Attorney Case File are re-uploaded to a SharePoint document library tied to the corresponding Dynamics 365 Account. The original file name, upload date, and attorney uploader are preserved in the SharePoint file metadata. For documents without SharePoint migration access, file references are stored as Notes attachments.

The Attorney Case File

Matter Custom Fields

maps to

Microsoft Dynamics 365 Sales

Custom Columns on Account or Custom Table

1:1
Fully supported

Any custom fields defined in The Attorney Case File for matters (e.g., Court Venue, Case Number, opposing Counsel, Statute of Limitations) are created as custom columns in Dataverse — either on the Account table or on a dedicated attorneycasefile_matter custom table depending on field purpose and cardinality.

The Attorney Case File

Calendar / Appointment

maps to

Microsoft Dynamics 365 Sales

Appointment (Activity)

1:1
Fully supported

Calendar entries and appointments from The Attorney Case File migrate as Dynamics 365 Appointments. The regarding field links to the parent Account or Contact. Original start/end times, subject, body, and organizer are preserved. Client-facing appointments with external attendees are migrated with the location field set to the client's address from the Contact record.

The Attorney Case File

Task / Reminder

maps to

Microsoft Dynamics 365 Sales

Task (Activity)

1:1
Fully supported

Tasks and reminders associated with matters map to Dynamics 365 Task records. The Regarding field points to the Account or Contact. Status (Open, Completed), Priority, Due Date, and Subject are transferred directly. Completed-at timestamps are preserved as custom datetime fields when available.

The Attorney Case File

Workflow / Automation

maps to

Microsoft Dynamics 365 Sales

Power Automate (no equivalent record)

1:1
Fully supported

The Attorney Case File workflow automations, email triggers, and document merge templates have no native equivalent in Dynamics 365. These must be rebuilt using Power Automate flows and Dynamics 365 templates post-migration. We export the workflow definitions as a reference document for your Dynamics 365 admin.

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.

The Attorney Case File logo

The Attorney Case File gotchas

High

No public API — extraction requires vendor coordination

Medium

Export envelope is limited to workbook-level records

Medium

Trust accounting data is outside the export scope

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

  • Matter-centric model requires splitting into Account + Custom Table in Dynamics 365

    The Attorney Case File stores client information, case details, billing, and documents all within a single matter record. Dynamics 365 Sales separates these concerns: client data lives in the Account entity, legal matter details need a custom Dataverse table (attorneycasefile_matter), and time entries require their own custom table. FlitStack AI decomposes the source matter into these separate Dataverse rows and re-links them via lookup fields. This means Dynamics 365 forms will need to be configured to display the related matter data from the custom table alongside the Account — a setup step that occurs before migration data lands.

  • Dynamics 365 does not have a native billing or time-tracking entity

    Time entries, billing rates, and invoices from The Attorney Case File have no native equivalent in Dynamics 365 Sales. The platform handles billing through Dynamics 365 Finance or through third-party add-ons. We create custom Dataverse tables (attorneycasefile_timeentry and attorneycasefile_invoice) that preserve the data for reference, but the financial workflow — sending invoices, tracking payments, managing trust accounts — must be designed in your Dynamics 365 billing model post-migration. This is a process decision, not a data-loss issue.

  • Document re-upload requires SharePoint site provisioning in Dynamics 365

    The Attorney Case File stores documents as attachments on matter records. Dynamics 365 stores documents in SharePoint Online document libraries linked via SharePointDocumentLocation records. Before migration, your Microsoft 365 tenant needs a SharePoint site provisioned and connected to Dynamics 365 via the SharePoint integration settings. Documents migrate as new file uploads to the corresponding Account folder, preserving the original file name and uploader timestamp in SharePoint file metadata. If your tenant does not have SharePoint Online, documents are stored as Note attachments with a 5 MB per-file limit.

  • Attorney and staff email resolution must complete before migration records land

    Dynamics 365 requires an OwnerId (SystemUser reference) on every record. The Attorney Case File stores attorney IDs internally. FlitStack AI matches source owner email addresses to Dynamics 365 user accounts using the SystemUser.emailaddress1 field. If an attorney in The Attorney Case File has no corresponding Dynamics 365 user account, their records are assigned to a designated fallback user and flagged in the pre-migration report. Your admin must provision missing Dynamics 365 user accounts before the migration run to avoid orphaned records.

  • Workflow automations and document merge templates do not migrate to Power Automate

    The Attorney Case File workflow rules (e.g., automatic reminder triggers, case status change notifications, template merge logic) are platform-specific and have no direct equivalent in Dynamics 365. These must be rebuilt as Power Automate flows or Dynamics 365 business process flows after migration. We export the workflow definitions as a structured reference document listing each rule's trigger, condition, and action, so your Dynamics 365 admin or consultant can rebuild them. Email templates and merge-field configurations also require Dynamics 365 Word template or Power Automate setup.

Migration approach

Six steps for a successful The Attorney Case File to Microsoft Dynamics 365 Sales data migration

  1. Provision Dynamics 365 environment and configure SharePoint integration

    Before migration data moves, your Microsoft 365 admin provisions a SharePoint Online site and enables the Dynamics 365 SharePoint integration via Settings > Document Management. We then create the custom Dataverse tables (attorneycasefile_matter, attorneycasefile_timeentry, attorneycasefile_invoice) and all required custom columns on the Account and Contact entities based on The Attorney Case File schema export. This step establishes the target schema so field-level mapping validates before any records load.

  2. Export The Attorney Case File data and resolve owner emails to Dynamics 365 users

    We extract all matters, client contacts, time entries, invoices, and document metadata from The Attorney Case File via CSV export or API query. Each attorney and staff owner email is matched against the Dynamics 365 SystemUser table by email address. Unmatched owners are reported to your admin with instructions to create the missing Dynamics 365 user accounts. This step gates the migration — no records load without confirmed owner resolution.

  3. Run a sample migration of 50–100 matters with field-level diff

    A representative slice of matters, contacts, time entries, and documents migrates first into your Dynamics 365 sandbox or development environment. We generate a field-level comparison report between source values and destination values, verifying that matter names, contact links, custom field data, and time entry amounts transferred correctly. Your team reviews the diff report and approves field mapping adjustments before the full migration run commits.

  4. Execute full migration with delta-pickup window and document re-upload

    The full record set loads into Dynamics 365 via Dataverse Web API batch operations, respecting API request limits. Documents attached in The Attorney Case File are downloaded and re-uploaded to the corresponding SharePoint Account folders, with original file names and uploader timestamps preserved in SharePoint metadata. During the cutover window (24–48 hours), any new matters or updated contacts created in The Attorney Case File are captured by the delta pickup run and merged into Dynamics 365. Audit logs record every operation; one-click rollback is available if reconciliation identifies data integrity issues.

Platform deep dives

Context on both ends of the pair

The Attorney Case File logo

The Attorney Case File

Source

Strengths

  • One-time pricing with no per-user per-month recurring cost for solo practitioners
  • Intuitive interface requiring minimal training for basic case management tasks
  • Responsive customer support cited across multiple user reviews
  • Customizable workbook structure adaptable to different practice areas
  • Designed specifically for attorneys rather than repurposed from a generic CRM

Weaknesses

  • No publicly documented API for programmatic data export or integration
  • Limited document management capabilities不适合 handling large case document volumes
  • Reported instability or lack of clear development roadmap in at least one review
  • May not scale for multi-party or highly complex litigation matters
  • No dedicated trust accounting or full practice accounting module
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 The Attorney Case File 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

    The Attorney Case File: Not publicly documented.

  • Data volume sensitivity

    B

    The Attorney Case File doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your The Attorney Case File 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 The Attorney Case File to Microsoft Dynamics 365 Sales data migrations

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

Can't find your answer?

Walk through your The Attorney Case File 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 The Attorney Case File to Dynamics 365 migrations complete in 48–72 hours for under 25,000 matter records. Larger setups with 100,000+ records, multiple custom matter fields, or extensive time entry histories extend to 7–10 days. The longest planning step is configuring the custom Dataverse tables and SharePoint document library before data validation runs. Dynamics 365 API request throttling (6,000 requests per user per minute in Enterprise) also affects batch migration throughput.

Adjacent paths

Related migrations to explore

Ready when you are

Move from The Attorney Case File.
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