CRM migration
Field-level mapping, validation, and rollback between OneAdvanced Legal and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
OneAdvanced Legal
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
10 of 11
objects map 1:1 between OneAdvanced Legal and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
48–72 hours
Overview
OneAdvanced Legal is a cloud-native practice and case management platform built for UK and Irish law firms. Its core objects — Client, Contact, Matter, Time Entry, Document, and Task — reflect legal-specific workflows: billable-hour tracking, matter-stage management, and compliant accounts integration. Microsoft Dynamics 365 Sales (built on Dataverse) models the same business relationships through Account, Contact, Lead, and Opportunity tables, plus custom tables for anything outside the standard CRM set. The two platforms share almost no schema overlap, so every migration field gets a named translation. FlitStack AI reads the OneAdvanced Legal API to extract Client records, their associated Contacts, active and historical Matters, billable Time Entries, and Documents. We map these to Dynamics 365 Sales Account and Contact records, then route Matters to either the native Opportunity table or a custom Matter table depending on whether your Dynamics 365 license tier allows it. Time Entries migrate as Task and Email records with the original duration, date, and fee-earner owner preserved as custom fields. Documents are downloaded and re-hosted in SharePoint or Dataverse file storage linked back to the parent record. Workflows, automations, and compliance-rule logic from OneAdvanced Legal do not transfer — we export them as human-readable JSON for a Dynamics 365 admin or Power Automate developer to rebuild against the new schema.
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
OneAdvanced Legal platform overview
Scorecard, SWOT, gotchas, and pricing for OneAdvanced Legal.
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 OneAdvanced Legal 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.
OneAdvanced Legal
Client
Microsoft Dynamics 365 Sales
Account
1:1OneAdvanced Legal Client records map directly to Dynamics 365 Account. Client name becomes Account Name. Registered address and billing address map to address fields. The firm's UK/Irish jurisdiction field migrates as a custom Option Set field on Account for compliance filtering.
OneAdvanced Legal
Contact
Microsoft Dynamics 365 Sales
Contact
1:1OneAdvanced Contact maps to Dynamics 365 Contact. The Contact's parent Client link becomes AccountId lookup. Primary solicitor and billing-contact flags translate as custom boolean fields on the Contact record. Multi-contact relationships per client collapse to primary ContactId plus Account Contact Roles.
OneAdvanced Legal
Contact
Microsoft Dynamics 365 Sales
Lead
1:manyOneAdvanced Contacts flagged as 'Prospect' or 'Referrer' with no active Matter route to Dynamics 365 Lead. Active matter holders route to Contact. The split logic uses a matter-count field aggregated before migration to determine the split point. Contacts without any historical or active matters qualify for Lead conversion workflows in Dynamics 365.
OneAdvanced Legal
Matter
Microsoft Dynamics 365 Sales
Opportunity (or custom Matter table)
1:1If Dynamics 365 is on the Enterprise or Premium tier, Matters map to a custom Matter__c table with Opportunity as the linked sales record. On Sales Professional (15-table limit), Matters map to Opportunity directly with a matter-type pick-list. Each Matter stage maps to an Opportunity StageName value via value-mapping per matter type.
OneAdvanced Legal
Matter
Microsoft Dynamics 365 Sales
Custom table (Matter__c)
1:1A custom Matter__c table is required on Sales Professional environments to hold OneAdvanced matter-specific fields: MatterType__c, MatterStage__c, ResponsibleFeeEarner__c, EstimatedValue__c, ReferralSource__c, and LegalAidReference__c. The table links back to the parent Account via AccountId lookup.
OneAdvanced Legal
Time Entry
Microsoft Dynamics 365 Sales
Task / Email
1:1Billable time entries from OneAdvanced Legal map to Dynamics 365 Task records with Type=' billable time'. Original duration in minutes maps to ActualDurationMinutes. Fee-earner owner maps by email match to Dynamics 365 User. Billing rate and billable/non-billable flag map to custom decimal and boolean fields on the Task.
OneAdvanced Legal
Task
Microsoft Dynamics 365 Sales
Task
1:1OneAdvanced Tasks map to Dynamics 365 Task records 1:1. Subject, Description, Due Date, Priority, and Status map by name. Owner resolved by email match. Tasks linked to a Matter carry the custom Matter__c lookup if the custom table is in use.
OneAdvanced Legal
Document
Microsoft Dynamics 365 Sales
SharePoint / Note / Attachment
1:1OneAdvanced Documents are downloaded from SharePoint-connected storage and re-hosted in the Dynamics 365 SharePoint integration. Each document is attached to the parent Matter (or Opportunity) record with the original filename and create-date preserved. Files larger than 25MB are chunked per Microsoft file-size limits.
OneAdvanced Legal
Matter Stage / Workflow
Microsoft Dynamics 365 Sales
Power Automate (rebuild required)
1:1OneAdvanced matter-stage automation and workflow rules have no native equivalent in Dynamics 365 Sales. We export the workflow definitions as a structured JSON file that maps each trigger-action pair to a Power Automate flow template. Rebuild is scoped separately from the data migration.
OneAdvanced Legal
Invoice / Bill
Microsoft Dynamics 365 Sales
Dynamics 365 Finance or external accounting system
1:1SAR-compliant billing records from OneAdvanced Legal cashier module do not map to Dynamics 365 Sales. We export invoice headers and line items as a structured CSV for import into Dynamics 365 Finance, Business Central, or the firm's preferred accounting platform. This step is scoped separately.
OneAdvanced Legal
User / Fee Earner
Microsoft Dynamics 365 Sales
SystemUser
1:1OneAdvanced fee-earner and staff user records resolve by email match against Dynamics 365 SystemUser. Unmatched users are flagged in a pre-migration report with the option to invite them to Dynamics 365 before the migration run. Inactive OneAdvanced users map to a 'Legacy User' placeholder contact for audit continuity.
| OneAdvanced Legal | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Client | Account1:1 | Fully supported | |
| Contact | Contact1:1 | Fully supported | |
| Contact | Lead1:many | Fully supported | |
| Matter | Opportunity (or custom Matter table)1:1 | Fully supported | |
| Matter | Custom table (Matter__c)1:1 | Fully supported | |
| Time Entry | Task / Email1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Document | SharePoint / Note / Attachment1:1 | Fully supported | |
| Matter Stage / Workflow | Power Automate (rebuild required)1:1 | Fully supported | |
| Invoice / Bill | Dynamics 365 Finance or external accounting system1:1 | Fully supported | |
| User / Fee Earner | SystemUser1: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.
OneAdvanced Legal gotchas
Limited public API documentation complicates automated extraction
Trust account transaction sequencing risk at cutover
Custom properties and bespoke workflows are not visible in standard exports
National Will Register data sits outside the main platform
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 source schema and target environment
FlitStack connects to the OneAdvanced Legal REST API to catalogue every active object type, custom field, and relationship. Simultaneously, we inspect the target Dynamics 365 environment — confirming the license tier, counting existing custom tables, and identifying record types already in use. If the target is on Sales Professional and the table count exceeds 15, we flag the overage before any extraction begins and recommend an Enterprise license upgrade.
Build the value-mapping plan and schema plan
Using the source audit, FlitStack generates a field-level mapping spreadsheet covering every object pair. For Matter-type-specific stage names, we produce a separate value-mapping sheet per record type. If a custom Matter__c table is required, we deliver the table schema (columns, types, relationships) for the Dynamics 365 admin to create before migration data is loaded. The mapping plan is reviewed and approved before extraction begins.
Extract, transform, and validate a sample slice
A representative slice of records — typically 200–500 per object type, including the firm's most complex matter type — is extracted from OneAdvanced, transformed per the approved mapping, and loaded into a Dynamics 365 sandbox. We generate a field-level diff showing every source value and its destination counterpart. The firm reviews the diff and confirms the mapping before the full run is scheduled.
Run full migration with delta-pickup window
All records — Client, Contact, Matter, Time Entry, Task, and Document — load into Dynamics 365 using the Bulk API. A delta-pickup window of 24–48 hours after the main run captures any records created or modified in OneAdvanced during the cutover period. Each operation is logged in the FlitStack audit trail. Owner resolution by email match is applied; unmatched owners are flagged in a pre-cutover report so the firm can invite users or assign a fallback owner before go-live.
Validate record counts, relationships, and document links
After the full run, FlitStack runs a reconciliation report comparing record counts per object type against the source export. Parent-child relationships (Client to Matter, Matter to Time Entry, Matter to Document) are verified via lookup field checks. Documents are spot-checked for file integrity. If any threshold is breached, one-click rollback reverts the Dynamics 365 environment to its pre-migration state so the team can investigate and re-run.
Platform deep dives
OneAdvanced Legal
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between OneAdvanced Legal and Microsoft Dynamics 365 Sales .
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across OneAdvanced Legal and Microsoft Dynamics 365 Sales .
Object compatibility
All 8 core objects map 1:1 between OneAdvanced Legal 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
OneAdvanced Legal: Not publicly documented.
Data volume sensitivity
OneAdvanced Legal 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 OneAdvanced Legal to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your OneAdvanced Legal 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 OneAdvanced Legal
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.