CRM migration
Field-level mapping, validation, and rollback between Bilr and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
Bilr
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
10 of 10
objects map 1:1 between Bilr and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
48–72 hours
Overview
Bilr is a legal billing and time-tracking platform organized around clients, matters, billable hours, and invoices. Microsoft Dynamics 365 Sales is a CRM organized around Accounts (companies), Contacts (individuals), Leads (prospects), and Opportunities (deals). The two data models diverge significantly: Bilr stores financial records natively, while Dynamics 365 Sales treats billing as a downstream ERP concern best handled by Dynamics 365 Business Central. We map Bilr client records to Dynamics 365 Account and Contact objects, matter records to a custom Matter table with a lookup to Account, time entries to custom Activity tables, and billing data to a custom Invoice or Billing Record table. Workflows, automation rules, and templates built in Bilr do not transfer — FlitStack exports Bilr workflow definitions as a reference document for your Dynamics 365 admin to rebuild in Power Automate. The migration uses Dynamics 365 Dataverse API calls, preserving original create dates and user ownership resolved by email match against Dynamics 365 user accounts.
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
Bilr platform overview
Scorecard, SWOT, gotchas, and pricing for Bilr.
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 Bilr 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.
Bilr
Client
Microsoft Dynamics 365 Sales
Account
1:1Bilr client records map to Dynamics 365 Accounts representing law firm clients or organizations. Client name, address, and contact information translate directly. Primary client type (individual vs. organization) determines whether a Contact record is also created alongside the Account. The mapping preserves the original client ID for referential integrity across the migration.
Bilr
Client Contact
Microsoft Dynamics 365 Sales
Contact
1:1Bilr contact records associated with clients map to Dynamics 365 Contacts linked to the corresponding Account via parentcustomerid. Multiple contacts per Bilr client translate to multiple Contact records sharing the same AccountId lookup in Dynamics 365. Each contact's email, phone, and role fields map to corresponding Dynamics 365 Contact columns. The parentcustomerid lookup ensures the hierarchical relationship is maintained.
Bilr
Matter
Microsoft Dynamics 365 Sales
Custom Matter Table
1:1Bilr matters have no direct CRM equivalent. We create a custom Matter table in Dynamics 365 with a lookup to Account. Matter number, title, status, responsible attorney, and billing arrangement fields migrate as custom columns on the Matter record. The lookup field links each Matter to its parent Account, and all original matter identifiers are retained for downstream reference.
Bilr
Time Entry
Microsoft Dynamics 365 Sales
Custom TimeEntry Table
1:1Billable hours logged in Bilr migrate to a custom TimeEntry table in Dynamics 365 linked to the Matter and the responsible Contact. Date, hours, billing rate, description, and billable/non-billable flags preserve as custom columns for reporting continuity. The TimeEntry records are linked to the Matter via a custom lookup field, and the responsible Contact is recorded as the owner for audit trail.
Bilr
Invoice
Microsoft Dynamics 365 Sales
Custom Invoice Table
1:1Bilr invoices migrate to a custom Invoice table linked to the Matter and Account. Invoice number, date, total amount, status (draft/sent/paid), and line items preserve as custom fields. Dynamics 365 Sales does not natively create invoices — firms typically use Business Central for full invoicing post-migration.
Bilr
Trust Transaction
Microsoft Dynamics 365 Sales
Custom TrustTransaction Table
1:1Bilr trust account transactions migrate to a custom TrustTransaction table linked to the Account. Transaction type (deposit/withdrawal), amount, date, and matter reference preserve as custom columns. Trust balance calculations are not replicated — Dynamics 365 does not handle trust accounting natively.
Bilr
Billing Rate / Fee Schedule
Microsoft Dynamics 365 Sales
Custom BillingRate Table
1:1Attorney and staff billing rates defined in Bilr migrate to a custom BillingRate table linked to Contact (for attorney records) or as a standalone table. Rate type (hourly/fixed/contingency) and amount preserve for reference in Dynamics 365 reports. The BillingRate table links to Contact for attorney rates or stands alone for firm-wide schedules. All original Bilr rate identifiers are retained to support reconciliation after migration.
Bilr
User / Attorney
Microsoft Dynamics 365 Sales
SystemUser
1:1Bilr users and attorneys resolve to Dynamics 365 SystemUser records by email address match. Unmatched users are flagged before migration — firms either pre-create Dynamics 365 user accounts or assign records to a fallback user during migration. Bilr role assignments map to Dynamics 365 security roles.
Bilr
Attachment / Document
Microsoft Dynamics 365 Sales
SharePoint / Note
1:1Documents attached to Bilr matters re-upload to Dynamics 365 SharePoint integration linked to the Matter Account or custom Matter record. Original filenames and attachment dates preserve. Microsoft SharePoint Document Center provides the storage layer for migrated files, and version history is retained where available.
Bilr
Workflow / Automation
Microsoft Dynamics 365 Sales
Power Automate / Dynamics Workflow
1:1Bilr workflows, automation rules, and templates have no direct equivalent in Dynamics 365. We export Bilr workflow definitions as a structured JSON reference document for the firm's Dynamics 365 admin to rebuild using Power Automate or Dynamics 365 native workflows post-migration.
| Bilr | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Client | Account1:1 | Fully supported | |
| Client Contact | Contact1:1 | Fully supported | |
| Matter | Custom Matter Table1:1 | Fully supported | |
| Time Entry | Custom TimeEntry Table1:1 | Fully supported | |
| Invoice | Custom Invoice Table1:1 | Fully supported | |
| Trust Transaction | Custom TrustTransaction Table1:1 | Fully supported | |
| Billing Rate / Fee Schedule | Custom BillingRate Table1:1 | Fully supported | |
| User / Attorney | SystemUser1:1 | Fully supported | |
| Attachment / Document | SharePoint / Note1:1 | Fully supported | |
| Workflow / Automation | Power Automate / Dynamics Workflow1: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.
Bilr gotchas
No trust accounting support is a hard blocker for IOLTA firms
Limited workflow and template customization
Per-seat pricing model is migration-cost-sensitive
Export scope discovery is required before migration
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
Extract Bilr data via API
FlitStack connects to Bilr using your API credentials and exports all primary objects: client records, contact records, matters, time entries, invoices, trust transactions, billing rates, and user accounts. We also extract custom field definitions and workflow templates as JSON metadata. The extraction runs read-only — your team continues working in Bilr during this phase. A data profiling report flags duplicates, missing required fields, and inconsistent data before transformation begins.
Create Dynamics 365 custom tables and fields
Before loading data, FlitStack creates the custom Matter, TimeEntry, Invoice, TrustTransaction, and BillingRate tables in your Dynamics 365 Dataverse environment using the Dynamics 365 administration API. Custom columns are added to each table matching Bilr field names and data types. If your Dynamics 365 license is Sales Professional, we identify the custom table count during discovery and escalate any 15-table-limit conflicts before schema creation begins.
Resolve owners and map user accounts
Bilr user records are matched against Dynamics 365 SystemUser records by internal email address. Unmatched users are flagged in a resolution report with full name, Bilr role, and email — your admin creates corresponding Dynamics 365 accounts or assigns a fallback owner before migration. User role mappings from Bilr translate to the nearest Dynamics 365 security roles (Attorney, Paralegal, Billing, Admin) so permissions are functional from day one.
Run sample migration with field-level diff
A representative slice — typically 200–500 records spanning clients, matters, time entries, and invoices — migrates to a Dynamics 365 sandbox environment first. FlitStack generates a field-level diff comparing source values to destination field values, custom table record counts, and lookup resolution status. You review the diff and confirm that Matter-to-Account lookups resolved correctly, time entries link to the right Matter records, and invoice totals match Bilr originals before the full migration commits.
Execute full migration with delta-pickup window
The full migration loads clients, contacts, matters, time entries, and invoices into your production Dynamics 365 environment in dependency order — Accounts first, then Contacts, then custom Matter records, then time entries and invoices linked by lookup. A delta-pickup window of 24–48 hours captures any Bilr records created or modified during cutover. Audit logs record every operation; one-click rollback reverts the Dynamics 365 environment to its pre-migration state if reconciliation fails.
Deliver workflow reference document for Power Automate rebuild
FlitStack exports your Bilr workflow definitions, automation rules, and template configurations as a structured JSON reference file organized by workflow name, trigger type, and action sequence. Your Dynamics 365 admin uses this document to rebuild equivalent flows in Power Automate or Dynamics 365 native workflows. FlitStack does not automate this rebuild — workflow recreation is a configuration step handled by your admin or a Dynamics 365 implementation partner.
Platform deep dives
Bilr
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Bilr and Microsoft Dynamics 365 Sales .
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
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
Bilr: Not publicly documented — typical SaaS limits assumed and confirmed during scoping.
Data volume sensitivity
Bilr 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 Bilr to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your Bilr 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 Bilr
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.