CRM migration
Field-level mapping, validation, and rollback between Fulcrum Snap and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
Fulcrum Snap
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
12 of 12
objects map 1:1 between Fulcrum Snap and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
48–72 hours
Overview
Fulcrum Snap is a legal/professional-services management platform built on SAP that stores clients, matters, contacts, time entries, and e-billing records in a flat, table-oriented schema designed for law-firm operations. Microsoft Dynamics 365 Sales is a CRM built on Dataverse that organizes data around Accounts, Contacts, Leads, and Opportunities with relational lookup links, a 15-table custom limit on Professional tier, and a Dataverse Web API capped at approximately 100,000 requests per tenant per day. The migration carries everything Fulcrum Snap stores natively — client records, matter hierarchies, contact associations, time entries, and audit trails — into Dynamics 365 Sales custom tables and standard entities. The harder problems are translating the matter-centric object model into a CRM relational schema, preserving custom field definitions that exceed D365 Professional's 15-table ceiling, handling user resolution against Dataverse systemusers, and routing the e-billing record chain to a custom table structure that your finance team can reconstruct post-migration. We run a test migration with field-level diff before the full cutover; a delta-pickup window captures any Fulcrum Snap changes during the switch.
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
Fulcrum Snap platform overview
Scorecard, SWOT, gotchas, and pricing for Fulcrum Snap.
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 Fulcrum Snap 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.
Fulcrum Snap
Client
Microsoft Dynamics 365 Sales
Account
1:1Direct map. Fulcrum Snap clients with billing addresses and industry classifications translate to D365 Accounts. Client status (Active/Inactive) is preserved as a custom field on the Account record. Records without a billing address land as Accounts with an empty address block and are flagged for manual completion.
Fulcrum Snap
Contact
Microsoft Dynamics 365 Sales
Contact
1:1Direct map. Fulcrum Snap contact properties — name, email, phone, role on matter — translate to D365 Contact fields. Multi-contact associations per matter are preserved as Contact-to-Account relationships. Each contact's primary client link is resolved via the AccountId lookup; secondary client associations surface as additional Account Contact Relationships in D365.
Fulcrum Snap
Matter
Microsoft Dynamics 365 Sales
Custom Table (Matter) or Opportunity
1:1Matters are the core Fulcrum Snap entity with client link, matter number, description, status, responsible attorney, and billing arrangement. D365 Sales has no native matter object; we create a custom Matter table in Dataverse. If your firm plans to use Opportunity for billing tracking, we map the matter number to Opportunity.Name and the billing arrangement to custom fields on the Opportunity — this requires Enterprise or Premium tier for the additional custom table beyond the 15-table Professional limit.
Fulcrum Snap
Matter Assignment
Microsoft Dynamics 365 Sales
Custom Table (MatterAssignment)
1:1Fulcrum Snap matter assignments track which staff members are allocated to a matter with role and hourly rate. D365 has no native equivalent. We create a MatterAssignment custom table linked to both the Matter table and the Contact (staff member). Hourly rate is preserved as a custom currency field; role is preserved as a custom picklist. This table is essential for billing reconstruction in D365.
Fulcrum Snap
Time Entry
Microsoft Dynamics 365 Sales
Activity (Phone Call, Task) or Custom Table (TimeEntry)
1:1Fulcrum Snap time entries include date, duration, attorney, matter link, description, billable/non-billable flag, and amount. D365 standard Activities (Task, PhoneCall) do not capture billable amount or matter link natively. We create a TimeEntry custom table linked to the Matter table; billable amount is preserved as a custom currency field. Standard D365 Activities are created alongside for calendar tracking where a date-only record is sufficient.
Fulcrum Snap
Bill / Invoice
Microsoft Dynamics 365 Sales
Custom Table (Bill) or Opportunity Product
1:1Fulcrum Snap stores e-billing records with invoice number, matter link, line items, total amount, status, and payment date. D365 Sales has no native billing entity — Invoice is available in D365 Sales Hub but requires the Sales Hub add-on and is oriented toward sales quotes, not legal billing. We create a Bill custom table preserving all invoice fields; line items map to BillLine custom table with description, quantity, unit price, and tax. Post-migration, your team can build Power Automate flows to sync Bill records to Business Central or a dedicated accounting tool.
Fulcrum Snap
Trust Record
Microsoft Dynamics 365 Sales
Custom Table (TrustRecord)
1:1Fulcrum Snap tracks IOLTA and client trust account balances. D365 Sales has no trust accounting capability — this is an SAP-side function. We preserve trust records as a read-only custom table for audit trail purposes. Reconciliation must be handled in SAP or your designated accounting system post-migration; FlitStack does not migrate live financial balances, only the record metadata.
Fulcrum Snap
Document / Attachment
Microsoft Dynamics 365 Sales
SharePoint (connected to D365) or Note
1:1Fulcrum Snap document attachments link to matters, clients, or contacts. D365 Sales connects natively to SharePoint Online for document storage. We upload documents to a SharePoint library structured by Account and Matter, then create D365 Note records pointing to the SharePoint URLs. Original file names and upload timestamps are preserved. Inline images are downloaded and rehosted in SharePoint.
Fulcrum Snap
Staff / User
Microsoft Dynamics 365 Sales
SystemUser
1:1Fulcrum Snap staff records include name, email, role, department, and billing rate. D365 user accounts are stored as systemuser records in Dataverse. We match Fulcrum Snap staff by email to existing D365 systemusers; unmatched staff are flagged as pending-user records. Role and department become custom fields on the systemuser record; billing rate is preserved on the MatterAssignment table.
Fulcrum Snap
Custom Field (any Fulcrum Snap entity)
Microsoft Dynamics 365 Sales
Custom Field (Dataverse attribute)
1:1Fulcrum Snap custom fields on any entity — client, matter, time entry, bill — are translated to Dataverse custom attributes. D365 applies a publisher prefix (new_ or a custom prefix based on your solution publisher) to all custom attribute names. We document the full attribute name mapping before migration so your D365 admin can configure forms and views with the correct field references.
Fulcrum Snap
Audit Log / Change History
Microsoft Dynamics 365 Sales
Custom Field or Audit Log
1:1Fulcrum Snap maintains a full change-audit trail on matters, time entries, and bills. D365's native audit log tracks schema changes and record modifications at the platform level but does not replicate Fulcrum Snap's application-level audit history. We preserve create-date, last-modified-date, and modified-by-user on every migrated record as custom datetime and lookup fields. Full audit chain reconstruction is available as an add-on service.
Fulcrum Snap
Matter Status / Workflow Step
Microsoft Dynamics 365 Sales
Custom Picklist or Opportunity Status
1:1Fulcrum Snap matter workflows have status values (Open, In Progress, Pending Review, Closed, Billed) and custom workflow steps. D365 Opportunity has a native StageName picklist scoped by business process. We map Fulcrum Snap matter status values to a custom picklist on the Matter table (or Opportunity StageName if using Opportunities for matters); custom workflow steps require rebuilding in D365 Power Automate — we export the workflow definitions as a rebuild reference.
| Fulcrum Snap | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Client | Account1:1 | Fully supported | |
| Contact | Contact1:1 | Fully supported | |
| Matter | Custom Table (Matter) or Opportunity1:1 | Fully supported | |
| Matter Assignment | Custom Table (MatterAssignment)1:1 | Fully supported | |
| Time Entry | Activity (Phone Call, Task) or Custom Table (TimeEntry)1:1 | Fully supported | |
| Bill / Invoice | Custom Table (Bill) or Opportunity Product1:1 | Fully supported | |
| Trust Record | Custom Table (TrustRecord)1:1 | Fully supported | |
| Document / Attachment | SharePoint (connected to D365) or Note1:1 | Fully supported | |
| Staff / User | SystemUser1:1 | Fully supported | |
| Custom Field (any Fulcrum Snap entity) | Custom Field (Dataverse attribute)1:1 | Fully supported | |
| Audit Log / Change History | Custom Field or Audit Log1:1 | Fully supported | |
| Matter Status / Workflow Step | Custom Picklist or Opportunity Status1: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.
Fulcrum Snap gotchas
SAP HANA schema complexity requires careful data mapping
Conflicts-denial flags block Matter recreation
Immutable time entries cannot be corrected post-sync on field app
Snap Insights dashboards are not migratable data
Custom fields schema must be extracted 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
Map source schema and design D365 custom table structure
FlitStack AI reviews the Fulcrum Snap data export — typically a full CSV or JSON export of all tables — and designs the D365 custom table schema. We identify every entity (Matter, Bill, TrustRecord, etc.), map custom fields with their D365 attribute names including the publisher prefix (new_), and calculate whether your D365 tier supports the total custom table count. We deliver a schema design document before any data moves so your D365 admin can create the tables, fields, and relationships in the target environment first.
Cleanse source data and resolve staff-to-systemuser links
Fulcrum Snap exports often contain duplicate client records, inconsistent date formats (MM/DD/YYYY vs ISO), and unmapped pick-list values. We run a pre-migration data quality pass — deduplication, date normalization to UTC, value-mapping of status fields — and match Fulcrum Snap staff by email against D365 systemusers. Staff without a D365 user account are flagged for your admin to provision before the migration run. No record lands in D365 without a resolved owner.
Migrate in dependency order: Accounts → Contacts → Matters → Time Entries → Bills
D365's relational model requires foreign keys to resolve at insert time — a Contact must have an AccountId, a TimeEntry must have a MatterId, a Bill must have a MatterId. We sequence the migration so parent records are created before child records. We run the migration in parallel where dependencies allow, but the chain Accounts → Contacts → Matters → Time Entries → Bills is sequential by necessity. Document attachments upload to SharePoint after the parent record is confirmed in D365.
Run a sample migration with field-level diff on 100–500 records
Before committing the full data set, we migrate a representative slice spanning all entity types — typically 100–500 records across clients, contacts, matters, time entries, and bills. We generate a field-level diff comparing source values against destination field values, surfacing any missing mappings, truncated text fields, or incorrect pick-list values. Your team reviews the diff and signs off before the full migration run commits. This step catches the majority of mapping errors before they affect production data.
Execute full migration with delta-pickup window and audit log
The full migration runs against D365 using the Dataverse Web API with batch-throttling against the 100K request/day limit. A delta-pickup window — typically 24–48 hours — captures any Fulcrum Snap records created or modified during the cutover. FlitStack AI maintains a full audit log of every insert, update, and association operation. One-click rollback is available if reconciliation fails. After the migration, we deliver a reconciliation report comparing record counts and key field totals between Fulcrum Snap and D365 so your team can confirm data completeness before going live.
Platform deep dives
Fulcrum Snap
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 Fulcrum Snap 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
Fulcrum Snap: Rate limits are documented in Fulcrum's Acceptable Use Policy and enforced per-org by the operations team; specific per-minute thresholds are not publicly disclosed.
Data volume sensitivity
Fulcrum Snap 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 Fulcrum Snap to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your Fulcrum Snap 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 Fulcrum Snap
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.