Migrate your Fulcrum Snap data

Clients are the top-level entity in Fulcrum Snap, holding firm-level details, billing addresses, and master contact associations. We map them 1:1 into destination CRM contacts or account objects, preserving any related matter counts as a custom property.

Matters are the core legal-workflow object tied to a Client, holding status, practice-area codes, responsible attorneys, and billing arrangements. We migrate Matters as structured records, flagging any open WIP or active billing periods that affect downstream financial reconciliation.

Time Entries are effective-dated, immutable billing records linked to a Matter and an Owner. We preserve the original entry date, duration, billable/non-billable flag, and narrative text, mapping them to time-entry or activity objects in the destination platform.

WIP represents unbilled time and cost aggregates tied to a Matter. Fulcrum Snap surfaces WIP as a live financial value rather than a discrete record; we extract WIP snapshots at migration time and recreate them as billing entries or credit memos in the destination system.

Billing Records are generated from WIP and time entries and carry invoice numbers, line items, tax codes, and payment status. We map them to invoice or billing objects, noting that SAP's invoice numbering sequence must not conflict with existing numbers in the destination ERP.

Conflicts records track intake-stage conflict checks against Client and Matter entities. They may contain adverse-party names, check dates, and clearance/denial flags. We export these as audit records; any 'denied' conflicts must be resolved before the Matter can be recreated in the destination system.

Intake records capture the onboarding workflow for a new Client or Matter — questionnaires, approval steps, and engagement-letter status. We map intake forms to the destination's equivalent onboarding or NBI objects and preserve completion state.

Fulcrum Snap supports custom fields on Matters, Clients, and other objects via its configuration layer. We extract the full custom-field schema at migration scoping and map values into destination custom properties, handling type differences (picklist vs. free-text) explicitly.

Documents attached to Matters or Clients — engagement letters, pleadings, invoices — are stored in SAP content repositories or linked file paths. We export them as binary blobs or URL references and re-attach them to the corresponding destination records.

User and Attorney records carry role, billing rate, department, and license-status data. We map them to owner or user objects in the destination, preserving department assignments and any SSO/SCIM identity links from the Elite tier.

Open AP and AR records, payment histories, and trust account movements live in the SAP financials layer. We extract these as structured line items and map them to the destination ERP's chart of accounts, preserving payment status and remaining balances.

Fulcrum Snap maintains a material repository used in e-billing and cost-tracking workflows. We export the material list with SKU, description, and pricing tiers, mapping them to the destination's items or services catalog.

Shipping methods are used in e-billing and invoice delivery contexts. We export the active method list and re-create it in the destination, noting that not all destination platforms support invoice-shipping-method logic.

Snap Insights dashboards are role-based analytics views built on top of the data model. These are configuration artifacts, not migratable data records — we do not transfer dashboard definitions. We do transfer the underlying data so dashboards can be rebuilt in the destination BI layer.