CRM migration
Field-level mapping, validation, and rollback between Link app and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
Link app
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
10 of 10
objects map 1:1 between Link app and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
48–72 hours
Overview
Link App is a legal-client communication platform centered on matters, document sharing, and threaded client messaging. Dynamics 365 Sales is a full sales-cycle CRM built on Dataverse with Accounts, Contacts, Leads, Opportunities, Activities, and a rich custom-table model. The two platforms share structural DNA at the contact level but diverge sharply at the record-type, pipeline, and activity-history layers. We map Link App Contacts to Dynamics 365 Contacts, Link App Companies to Dynamics 365 Accounts, Link App Matters to a custom Matters table or to Opportunities by case type, and Link App Messages/Documents to Dynamics 365 Activities and Notes respectively. Owner resolution runs by email match against Dynamics 365 users. Workflows, automation rules, and communication templates in Link App do not migrate — we export their definitions as a rebuild reference for your Dynamics 365 admin. Migration uses the Dynamics 365 Web API and Bulk API, respecting Dataverse request allocation limits. Delta-pickup captures any Link App records modified during the cutover window.
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
Link app platform overview
Scorecard, SWOT, gotchas, and pricing for Link app.
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 Link app 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.
Link app
Contact (Client)
Microsoft Dynamics 365 Sales
Contact
1:1Link App Client records map directly to Dynamics 365 Contacts. The Contact's primary Account (Law Firm) resolves by email domain match to the corresponding Dynamics 365 Account record. Clients without a firm affiliation land as Contacts with no AccountId and are flagged for manual review.
Link app
Company (Law Firm / Client Organization)
Microsoft Dynamics 365 Sales
Account
1:1Link App law firm and client organization records map to Dynamics 365 Accounts with comprehensive field preservation. The Account's physical address, industry classification (Legal Services), and employee count transfer directly as standard Dynamics 365 fields. Parent-account hierarchies in Link App map to the Account.ParentId field to maintain organizational structure in the target CRM.
Link app
Matter
Microsoft Dynamics 365 Sales
Custom Table: Matter__c (or Opportunity by type)
1:1Link App Matters have no direct Dynamics 365 equivalent. We create a custom Matter__c Dataverse table linked to the Account (client firm) and Contact (responsible attorney). Matter fields (type, status, open date, close date, billing arrangement) map to custom columns on the Matter__c table. If the firm uses a deal-centric view, Matters can alternatively map to Opportunities with a Matter_Type__c custom field.
Link app
Message (Client Communication Thread)
Microsoft Dynamics 365 Sales
Activity (Email or Phone Call)
1:1Link App message threads are flattened into Dynamics 365 Activities. Each message in a thread becomes a separate Task (for non-email messages) or an Email activity with the original sent-at timestamp and participant list preserved. Thread context is maintained by linking all activities to the same Matter__c record. Attachments on messages re-upload as Note attachments.
Link app
Document (File Attachment)
Microsoft Dynamics 365 Sales
Note (Annotation)
1:1Link App documents and file uploads migrate as Dynamics 365 Notes (annotations) attached to the parent Contact, Account, or Matter__c record matching the Link App context. File size limits follow Dataverse constraints. We re-upload documents to SharePoint if your Dynamics 365 environment uses SharePoint integration.
Link app
Attorney / Staff User
Microsoft Dynamics 365 Sales
SystemUser
1:1Link App user accounts resolve to Dynamics 365 users by email address match. The Link App user role (Attorney, Paralegal, Admin) maps to a corresponding Dynamics 365 Security Role assigned by your admin. Unmatched users are flagged and can be invited to Dynamics 365 before the migration runs.
Link app
Matter Status (Open, Pending, Closed)
Microsoft Dynamics 365 Sales
Matter__c.Status__c (Custom Picklist)
1:1Link App matter status values map to a custom pick-list on the Matter__c table. Each value translates by name (Open → Open, Pending → Pending Review, Closed → Closed Won/Lost). Status-change timestamps are preserved as custom datetime fields on the Matter__c record.
Link app
Custom Field (Legal-specific)
Microsoft Dynamics 365 Sales
Custom Column on Target Table
1:1Link App custom fields (e.g., Court_District__c, Billing_Arrangement__c, Referred_By__c) are read from the Link App schema export and created as matching Dataverse columns on the appropriate table. Field type is inferred from the data (text, picklist, date, number) and validated against Dynamics 365 column-type constraints.
Link app
Billing / Invoice Record
Microsoft Dynamics 365 Sales
Custom Table: Billing__c (or Opportunity Product)
1:1Link App billing and invoice records have no direct Dynamics 365 Sales equivalent — Dynamics 365 Sales is a CRM, not a billing system. We preserve billing records as a custom Billing__c table linked to Matter__c and Contact for reference. If the firm uses Dynamics 365 Business Central for accounting, we surface the mapping for ERP integration.
Link app
Tag / Label (e.g., Practice Area)
Microsoft Dynamics 365 Sales
Custom Picklist on Matter__c or Contact
1:1Link App tags that categorize matters across practice areas such as Family Law, Litigation, Corporate, and Immigration migrate as a custom Practice_Area__c pick-list on the Matter__c table. Contact-level tags and classifications map to a custom Contact_Type__c pick-list on the Contact record. We deduplicate tag values during migration to prevent redundant pick-list options in the target system.
| Link app | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Contact (Client) | Contact1:1 | Fully supported | |
| Company (Law Firm / Client Organization) | Account1:1 | Fully supported | |
| Matter | Custom Table: Matter__c (or Opportunity by type)1:1 | Fully supported | |
| Message (Client Communication Thread) | Activity (Email or Phone Call)1:1 | Fully supported | |
| Document (File Attachment) | Note (Annotation)1:1 | Fully supported | |
| Attorney / Staff User | SystemUser1:1 | Fully supported | |
| Matter Status (Open, Pending, Closed) | Matter__c.Status__c (Custom Picklist)1:1 | Fully supported | |
| Custom Field (Legal-specific) | Custom Column on Target Table1:1 | Fully supported | |
| Billing / Invoice Record | Custom Table: Billing__c (or Opportunity Product)1:1 | Fully supported | |
| Tag / Label (e.g., Practice Area) | Custom Picklist on Matter__c or Contact1: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.
Link app gotchas
No public API for automated bulk export
Document binaries may require separate file-level extraction
Case feed chronology does not map directly to standard CRM activity models
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
Discover Link App schema and export configuration
We connect to your Link App instance using scoped read access (no write permissions required) and extract the full object schema — all standard and custom fields, relationship definitions, and user list. We also export a representative sample of records (100–500 across Contacts, Companies, Matters, Messages, Documents) to validate data shapes before committing to a full run. This step produces a Link App field inventory that becomes the basis for the mapping specification.
Design Dynamics 365 schema and mapping specification
Based on the Link App field inventory, we design the Dynamics 365 target schema: custom Matter__c table with all custom columns, field-type validation, and pick-list option sets. We produce a written mapping specification document that lists every source field, its target column, mapping type (direct, value-mapping, custom_field_required), and any transformation notes. Your Dynamics 365 admin reviews and approves the specification before we create any columns in your environment.
Create Dataverse custom columns and validate relationships
We create the custom columns and tables in your Dynamics 365 Sales environment using the Dataverse Web API. If you use Sales Professional, we verify the 15-table limit is not exceeded. We also create any required N:1 lookup relationships (Matter__c to Account, Matter__c to Contact) and validate that pick-list values exist for every value-mapped field. This step runs in a sandbox or non-production environment first if one is available.
Run sample migration with field-level diff
A representative slice of Link App records (typically 200–500 spanning all object types) migrates to Dynamics 365 Sales. We generate a field-level diff comparing source values against destination values for every mapped field. You review the diff and approve the mapping before the full run. Any field that fails validation (truncated values, failed lookups, missing pick-list matches) is corrected in the mapping specification before proceeding.
Execute full migration with delta-pickup window
The full Link App dataset migrates to Dynamics 365 Sales using the approved mapping. A delta-pickup window (24–48 hours) runs concurrently — any Link App records created or modified during the migration cutover are captured and applied to Dynamics 365. Owner resolution by email match is applied throughout; records without a matched user are flagged in the audit log. After migration, we run a reconciliation report comparing record counts and field-population rates against the Link App source.
Platform deep dives
Link app
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between Link app and Microsoft Dynamics 365 Sales .
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Link app and Microsoft Dynamics 365 Sales .
Object compatibility
All 8 core objects map 1:1 between Link app 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
Link app: Not publicly documented..
Data volume sensitivity
Link app 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 Link app to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your Link app 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 Link app
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.