CRM migration

Migrate from Bilr to Microsoft Dynamics 365 Sales

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 logo

Bilr

Source

Microsoft Dynamics 365 Sales

Destination

Microsoft Dynamics 365 Sales  logo

Compatibility

100%

10 of 10

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

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Bilr logo

Bilr

What's pushing teams away

  • No trust accounting capability means firms subject to IOLTA requirements must run a separate system or leave the platform entirely
  • Limited customization options for templates and workflows frustrate firms with non-standard billing arrangements or practice-area-specific needs
  • Mid-tier and Advanced pricing at $45–55 per user per month scales cost-prohibitively for larger firms evaluating against all-in-one legal practice management suites
  • Smaller ecosystem and fewer integrations compared to dominant legal platforms creates friction for firms needing calendar, document, or accounting sync

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

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

maps to

Microsoft Dynamics 365 Sales

Account

1:1
Fully supported

Bilr 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

maps to

Microsoft Dynamics 365 Sales

Contact

1:1
Fully supported

Bilr 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

maps to

Microsoft Dynamics 365 Sales

Custom Matter Table

1:1
Fully supported

Bilr 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

maps to

Microsoft Dynamics 365 Sales

Custom TimeEntry Table

1:1
Fully supported

Billable 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

maps to

Microsoft Dynamics 365 Sales

Custom Invoice Table

1:1
Fully supported

Bilr 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

maps to

Microsoft Dynamics 365 Sales

Custom TrustTransaction Table

1:1
Fully supported

Bilr 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

maps to

Microsoft Dynamics 365 Sales

Custom BillingRate Table

1:1
Fully supported

Attorney 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

maps to

Microsoft Dynamics 365 Sales

SystemUser

1:1
Fully supported

Bilr 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

maps to

Microsoft Dynamics 365 Sales

SharePoint / Note

1:1
Fully supported

Documents 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

maps to

Microsoft Dynamics 365 Sales

Power Automate / Dynamics Workflow

1:1
Fully supported

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

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.

Bilr logo

Bilr gotchas

High

No trust accounting support is a hard blocker for IOLTA firms

Medium

Limited workflow and template customization

Medium

Per-seat pricing model is migration-cost-sensitive

Low

Export scope discovery is required before migration

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

  • Billing data has no native home in Dynamics 365 Sales CRM

    Dynamics 365 Sales does not include native invoice creation, trust accounting, or billing record management at the CRM tier. Bilr's core financial records — invoices, trust transactions, and billing arrangements — migrate to custom tables we create in the destination Dataverse environment. Firms requiring full accounting features need Dynamics 365 Business Central, which FlitStack can migrate separately from Bilr's accounting modules. Without Business Central, billing data in Dynamics 365 Sales is reference-only and does not drive financial workflows.

  • Workflows, templates, and automation rules do not transfer

    Bilr workflows for billing approvals, matter setup, and client onboarding have no equivalent in Dynamics 365 Sales. The Dynamics 365 equivalent is Power Automate for cloud flows and Dynamics 365 native workflows for record-level automation. FlitStack exports Bilr workflow definitions as a structured JSON reference file for your Dynamics 365 admin, but every workflow must be manually rebuilt. Templates for invoices, engagement letters, and matteropening checklists also do not migrate and require SharePoint template library recreation.

  • Dynamics 365 Sales Professional custom table limit constrains complex migrations

    Sales Professional caps custom tables at 15 — insufficient for a full Bilr migration with Matter, TimeEntry, Invoice, TrustTransaction, and BillingRate tables plus any custom fields on Account and Contact. Firms on Sales Professional must either upgrade to Enterprise or Premium (unlimited custom tables) or selectively migrate only primary objects, leaving advanced billing data for a later phase or a separate Business Central migration. FlitStack flags this during discovery and recommends the appropriate license tier before migration begins.

  • Owner resolution by email may leave unmapped attorneys

    Bilr user records resolve to Dynamics 365 SystemUser by email address match. If an attorney's email in Bilr does not correspond to an existing Dynamics 365 user account, their records land under a fallback user or remain unassigned. Firms with a large paralegal and contract attorney roster may have significant mismatches. FlitStack generates a pre-migration user resolution report listing matched users, unmatched users, and the recommended fallback owner so your admin can create accounts or assign proxies before the migration run.

Migration approach

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

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

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

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

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

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

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

Context on both ends of the pair

Bilr logo

Bilr

Source

Strengths

  • Purpose-built for legal billing workflows with time entry, expense tracking, and invoice generation within a single platform
  • Per-user pricing from $33.99/month provides a low barrier to entry for solo practitioners and small law firms
  • Three tiers (Basic, Pro, Advanced) offer a clear upgrade path as firm size and billing complexity grow
  • 24/5 support and on-demand training included across all tiers, differentiating from platforms that charge extra for support
  • Mobile apps on iOS and Android allow attorneys to log time and review bills from outside the office

Weaknesses

  • No trust accounting or IOLTA-compliant ledger means firms with client fund requirements cannot use Bilr as their sole financial system
  • Limited workflow customization and template flexibility frustrate firms with non-standard billing arrangements or practice-area-specific needs
  • Smaller third-party integration ecosystem compared to dominant legal practice management platforms creates friction for calendar, document, and accounting sync
  • Per-seat pricing scales cost linearly, which may become expensive for larger firms with many non-billing staff who need access
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 Bilr 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

    Bilr: Not publicly documented — typical SaaS limits assumed and confirmed during scoping.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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 consultation

Most Bilr to Dynamics 365 Sales migrations complete in 48–72 hours of processing time for under 25,000 total records across clients, matters, time entries, and invoices. Larger firms with 250,000+ records or complex multi-table custom schemas extend to 5–7 days. The longest planning step is creating Dynamics 365 custom tables and resolving user accounts before data loads — this discovery and schema preparation phase adds 1–2 weeks for straightforward setups or 3–5 weeks when Sales Professional license limits require upgrade coordination.

Adjacent paths

Related migrations to explore

Ready when you are

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