Skip to content
Get a quote

Clio to Salesforce migration

Moving from Clio to Salesforce Sales Cloud maps legal practice management data into a general-purpose CRM. FlitStack AI translates Clio matters, client records, billing structures, and time entries into Salesforce's Account-Contact-Opportunity object model, preserving matter-to-case relationships and original create timestamps while surfacing trust accounting and rate hierarchies as Salesforce custom fields for your admin to finalize.

Short answer

FlitStack AI migrates contact + accounts, case or opportunities, case type or recordtypeids, custom object: clio_billing__cs and custom object: time_entry__c or tasks from Clio to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 5–10 days for under 25,000 records.

By

Source Clio
DestinationSalesforce
Contact + AccountCase or OpportunityCase Type or RecordTypeIdCustom Object: Clio_Billing__cCustom Object: Time_Entry__c or Task
Mapped field by field · sample run · one-click rollback

What moves from Clio to Salesforce?

Clio organizes a law firm's data around Matters, Clients, Billing, and Activities — a legal-specific schema that has no direct equivalent in Salesforce's sales-oriented object model.

Read the full summary

The migration challenge is threefold: first, Clio Matters must map to Salesforce Cases (for case management) or Opportunities (for client development tracking) depending on your firm's workflow; second, Clio's billing constructs — trust accounts, flat-rate billing, rate hierarchies, and billing preferences — require custom fields in Salesforce since no native billing object exists in Sales Cloud; third, Clio's rate and expense structures need type-aware mapping to preserve financial data without creating a full accounting system in Salesforce. We migrate all contact records, matter records, documents, time entries, expenses, and custom fields via Clio's REST API (50 req/min rate limit managed with exponential backoff). Salesforce receives the data through Bulk API for high-volume loads and REST API for delta updates. Workflows, document templates, billing automation, and trust accounting rules do not migrate — we export them as JSON reference files for your Salesforce admin to rebuild using Flow and custom components. The delta-pickup window captures any matter changes made during cutover so Salesforce reflects Clio's final state at go-live.

transformed

Client → Contact + Account

Clio Clients are person-centric; they map to Salesforce Contacts with an optional Account for the associated organization.

How it maps

Individuals without a firm name attach to a default 'Individual Client' Account. Client billing preferences are preserved as custom fields on Contact. We also map the primary phone number to the Phone field and capture any secondary contact details in custom fields for downstream follow‑up.

transformed

Matter → Case or Opportunity

Clio Matters map to Salesforce Cases by default for matter management workflows.

How it maps

Firms tracking client development or revenue pipeline from matters map to Opportunities instead. The mapping decision is made during discovery; mixed mapping (some matters to Cases, some to Opportunities) is supported via a matter-type custom field.

value_mapping

Matter Type → Case Type or RecordTypeId

Clio matter types (Litigation, Corporate, Real Estate, Family Law, etc.) map to Salesforce Case Types or Opportunity Record Types depending on the chosen matter-to-object mapping.

How it maps

Each matter type requires its corresponding Record Type created in Salesforce before migration. If your firm uses custom matter type labels, we capture them in a separate picklist field and map each to the appropriate Salesforce type during data load.

custom_field_required

Bill / Invoice → Custom Object: Clio_Billing__c

Clio Bills have no Salesforce native equivalent.

How it maps

We create a custom object (Clio_Billing__c) with fields for invoice number, total amount, status, date, and linked matter. Trust accounting transactions (Ledger__c) are a separate custom object. Your admin maps these to an accounting integration post-migration.

transformed

Time Entry → Custom Object: Time_Entry__c or Task

Billable time entries migrate as a custom object linked to the matter Case.

How it maps

Non-billable time entries map to Salesforce Tasks with Type='Time Entry'. Each time entry preserves the original hours, rate, total, date, and user who recorded it. Rate hierarchy is preserved for post-migration billing rebuild reference.

direct

Expense → Custom Object: Expense__c

Clio expenses map directly to a custom Expense__c object with fields for amount, date, description, vendor, matter link, and user.

How it maps

Expenses do not map to Salesforce native expense features because Salesforce has none at the CRM level. We also capture the expense category and any billable flag so reporting can distinguish between client‑reimbursable and internal costs.

What moves12 objects
ClioSalesforce
  • ClientContacttransformed
  • MatterCase or Opportunitytransformed
  • Matter TypeCase Type or RecordTypeIdtransformed
  • BillCustom Object: Clio_Billing__ctransformed
  • Time EntryCustom Object: Time_Entry__c or Tasktransformed
  • ExpenseCustom Object: Expense__c1:1

+ 6 more in the mapping below

How Clio and Salesforce differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionClioSalesforce
Primary entity modelMatters are the central entity linking clients, billing, time, and documents in a legal matter contextCases and Opportunities share equal importance; Matters need to split into one or both based on firm workflow
Contact-company associationClients in Clio are contact-centric with one primary contact per matter; multi-contact matters supportedContacts require AccountId lookup; primary contact on matter maps to primary AccountId on Case
Billing and invoicingNative billing, trust accounting, flat-rate matters, and rate hierarchies with billing preferences per matterNo native billing; invoices, payments, and trust require custom objects or third-party integration
Document managementDocuments stored per matter with version history and client portal accessDocuments migrate to Salesforce Files/ContentVersion; portal access requires Salesforce Experience Cloud
Rate and expense structuresRate hierarchies (user, client, matter, activity-type), custom rates, and expense tracking per matterRates and expenses map to custom fields on Case or custom objects; no native hierarchy
Workflows and automationLegal-specific automations for intake, conflict checks, and matter milestonesWorkflows must be rebuilt in Salesforce Flow; no direct migration path
API architectureREST API at 50 req/min peak; paginated with ETags; rate limits increase off-peakBulk API for high-volume loads, REST for real-time; 100k daily API limit on Enterprise

Clio to Salesforce field mapping

The 30 most-used fields of 42 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.

Field mapping5 shown
ClioSalesforce
  1. first_nameClient FirstNameContact
  2. last_nameClient LastNameContact
  3. emailClient EmailContact
  4. phone_numberClient PhoneContact
  5. mobile_numberClient MobilePhoneContact
Clio fieldSalesforce fieldMappingNote
Client.first_nameContact.FirstNamedirect
Client.last_nameContact.LastNamedirect
Client.emailContact.Emaildirect
Client.phone_numberContact.Phonedirect
Client.mobile_numberContact.MobilePhonedirect
Client.titleContact.Titledirect
Client.address_line_1Contact.MailingStreetdirect
Client.cityContact.MailingCitydirect
Client.stateContact.MailingStatedirect
Client.postal_codeContact.MailingPostalCodedirect
Client.countryContact.MailingCountrydirect
Client.company_nameContact.Account.NametransformedClio company_name on a client creates or matches a Salesforce Account; contact attaches via AccountId lookup.
Client.client_idContact.Source_System_ID__ccustom_field_requiredClio's internal ID stored for traceability and delta-run de-duplication in Salesforce.
Client.created_atContact.Original_Create_Date__ccustom_field_requiredSalesforce CreatedDate is set at migration time; original Clio create date preserved as custom datetime.
Matter.display_numberCase.CaseNumberdirect
Matter.descriptionCase.Descriptiondirect
Matter.statusCase.Statusvalue_mappingMatter statuses (Open, Closed, Pending) map to Case statuses (New, Working, Closed) per your specified mapping table.
Matter.matter_typeCase.Typevalue_mappingClio matter types (Litigation, Corporate, Real Estate) map to Salesforce Case Type pick-list values.
Matter.practice_areaCase.Practice_Area__ccustom_field_requiredPractice area maps to a custom pick-list field on Case when Clio practice areas don't fit the Type pick-list.
Matter.open_dateCase.CreatedDatedirect
Matter.close_dateCase.ClosedDatedirect
Matter.responsible_attorneyCase.OwnerIdtransformedAttorney resolved by email match to Salesforce users; unmatched attorneys flagged before migration.
Matter.billable_amountCase.Billable_Amount__ccustom_field_requiredClio billable total migrates to custom currency field; not Salesforce native billing.
Matter.billing_preferenceCase.Billing_Preference__ccustom_field_requiredFlat-rate, hourly, or contingency billing preference stored as custom pick-list for rebuild reference.
Matter.matter_idCase.Source_System_ID__ccustom_field_requiredClio matter ID stored on Case for traceability and relationship preservation during delta runs.
Bill.invoice_numberClio_Billing__c.Invoice_Number__cdirect
Bill.totalClio_Billing__c.Total_Amount__cdirect
Bill.statusClio_Billing__c.Status__cvalue_mappingClio bill statuses (Draft, Sent, Paid, Written Off) map to custom pick-list values in Salesforce.
Bill.dateClio_Billing__c.Invoice_Date__cdirect
Bill.due_dateClio_Billing__c.Due_Date__cdirect

What to watch for in a Clio to Salesforce migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Clio rate hierarchies have no Salesforce native equivalent

Clio resolves billing rates through a hierarchy (custom rate → fixed rate → matter-based → client-based → user default) that applies at time-entry creation.

How we handle it

Salesforce has no native rate hierarchy mechanism — rates are static values on records. We preserve the full rate hierarchy structure as a JSON export and migrate effective rates at migration time as custom fields on Contact and Case. Your admin must decide whether to rebuild rate logic in Salesforce Flow or accept static rate fields. This is a structural gap that requires a business decision, not a data-loss problem.

high

Matter-to-object mapping decision changes the entire data model

Every Clio matter must map to either a Salesforce Case or Opportunity, and that decision determines the entire object hierarchy.

How we handle it

Mapping to Case gives you Salesforce's native case management features (Entitlements, Case Teams, SLAs) but limits pipeline visibility. Mapping to Opportunity gives you forecasting and pipeline views but loses case management features. Mixed mapping (some matters to Cases, some to Opportunities) is supported but requires a matter-type discriminator field (Practice_Area__c or custom) that your Salesforce admin must create and populate. The wrong initial decision forces a re-migration.

high

Trust accounting ledger entries require a separate custom object

Clio's trust accounting maintains a running balance of client funds held in trust — separate from bills and invoices.

How we handle it

Salesforce has no native trust accounting construct. We create a Clio_Trust_Ledger__c custom object that stores each trust transaction (type, amount, date, matter link, client link) so the transaction history is preserved. The running balance must be calculated by summing transactions; Salesforce does not maintain a live trust balance. Your admin should evaluate whether to connect this to an ERP or accounting integration post-migration.

medium

Clio's API rate limit of 50 req/min requires migration throttling

Clio's REST API enforces a 50 requests-per-minute limit during peak hours (with increases during off-peak).

How we handle it

This constrains data extraction speed significantly compared to Salesforce's Bulk API ingestion. We handle this by batching Clio reads with exponential backoff on 429 responses and running extraction during identified off-peak windows. For large firms (100k+ records), this can extend the extraction phase to several days. The delta-pickup window accounts for this by allowing in-flight records to sync after the main migration window closes.

medium

Document portal access requires Salesforce Experience Cloud

Document portal access requires Salesforce Experience Cloud.

How we handle it

Clio's client portal lets clients access documents directly within Clio. Salesforce Files attached to Cases via ContentDocumentLink are not accessible to external contacts without Salesforce Experience Cloud (formerly Community Cloud) licenses and a configured Customer Portal. If client document portal access is business-critical, Experience Cloud setup is a post-migration step. We migrate the document relationship and file content; portal access reconfiguration is outside the migration scope unless explicitly scoped.

How the migration runs

  1. Discover Clio schema and map to Salesforce object model

    We read your Clio account's custom fields, matter types, billing preferences, and rate hierarchies via the Clio API.

    What this step covers

    We then deliver a mapping specification document that defines the Matter-to-Case or Matter-to-Opportunity decision, custom field creation list for your Salesforce admin, and value-mapping tables for status and type pick-lists. Your admin creates the Salesforce custom fields and Record Types before we proceed to extraction.

  2. Extract all data from Clio with API throttling

    We authenticate against Clio's REST API using OAuth 2.0 and extract records in paginated batches, respecting the 50 req/min rate limit with exponential backoff.

    What this step covers

    Extraction runs during off-peak hours to maximize throughput. All records receive a source_system_id stamp and original_create_date preservation. Documents download as binary blobs for re-upload to Salesforce Files. We also log each batch with timestamps to facilitate audit trails and retry any failed requests automatically.

  3. Resolve attorneys and staff by email to Salesforce users

    Clio users (attorneys, paralegals, admins) are matched to Salesforce users by email address.

    What this step covers

    Unmatched users are flagged in a pre-migration report — your team either creates Salesforce user accounts for them or assigns their records to a fallback owner before migration. No matter or time entry lands in Salesforce without a valid OwnerId. We recommend verifying email domains and de‑activating any temporary accounts in Clio before the mapping phase to reduce mismatches.

  4. Run sample migration with field-level diff

    A representative slice (typically 200–500 records spanning matters, clients, bills, time entries, and documents) migrates first.

    What this step covers

    We generate a field-level diff showing source values next to destination values so you can verify status mapping, billing amounts, and relationship integrity before the full run commits. You approve the sample before we proceed to full extraction. The sample also validates data volume estimates and helps identify any missing custom fields early.

  5. Execute full migration with delta-pickup window

    Full data migration loads into Salesforce via Bulk API for high-volume record sets (Contacts, Cases) and REST API for complex objects (custom billing records, ContentVersion).

    What this step covers

    After initial load completes, a delta-pickup window (typically 24–48 hours) captures any records modified in Clio during cutover. Audit log records every operation; one-click rollback is available if reconciliation identifies data integrity issues. We also perform a final validation pass against source totals to confirm all matter and billing amounts transferred correctly.

Clio Salesforce
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · SalesforceRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

5–10 days for under 25,000 recordsTypical, smaller accounts
3–6 weeks for over 250,000 records or complex custom field setupsLarge or heavily customised accounts

Clio-to-Salesforce migrations price on record volume, matter complexity, and custom field count. Standard matter and client migrations with under 20 custom fields fall in the lower range. Firms with multi-matter types (litigation, transactional, corporate), trust accounting structures, or extensive rate hierarchies require additional mapping work and fall in the upper range. Document volume affects timeline but not price unless document re-hosting with Salesforce Files requires significant transformation. We include a field-level diff sample and delta-pickup window in every engagement. Pricing also reflects the need for custom object creation, testing cycles, and post-migration verification to ensure data integrity. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Clio to Salesforce →

Why teams move from Clio to Salesforce

  • Clio's templated reporting hits a ceiling for firms tracking multi-practice metrics in a single dashboard. Salesforce's customizable reports, joined views, and Tableau integration handle firm-wide analytics without Operations Hub pricing tiers. Firms with more than 15 attorneys report this as the first significant friction point in Clio at scale.
  • Multi-office or multi-practice firms using Clio find its practice-area module system limiting for shared client records and cross-firm reporting. Salesforce's multi-entity models and sharing rules let different offices or practice groups see only their data while leadership sees the full picture — a structural advantage Clio cannot match without significant customization.
  • Clio's integrations require workarounds for non-legal business tools like accounting software, HR systems, or enterprise analytics platforms. Salesforce's AppExchange ecosystem and native integrations with Slack, DocuSign, HubSpot Marketing, and ERP connectors eliminate those gaps. Firms already using Salesforce for other departments cite this as a consolidation driver.
  • Growing firms hit Clio's per-user pricing and feature tiers faster than expected as they add practice areas, client types, or matter complexity. Salesforce's tier model scales differently — more users at the same tier cost less per seat than adding Clio's higher tiers, and the feature set expands with each edition rather than requiring add-ons.
  • Acquired a firm running Salesforce or consolidating legal ops under a parent company's CRM standard. The legal data migrates into the parent org's object model so matter history, client relationships, and financial records appear in the same system the rest of the business uses.

Questions, answered

Clio to Salesforce migration questions

How long does a Clio to Salesforce migration take?

Most Clio-to-Salesforce migrations complete within 5–10 days of clock time for under 25,000 records. Firms with 250,000+ records or complex billing structures (trust accounting, multi-tier rate hierarchies, extensive custom fields) extend to 3–6 weeks. The mapping specification and Salesforce schema setup phase is the longest planning step — actual data extraction and loading runs faster once schema decisions are finalized.

Will my Clio workflows and automations migrate to Salesforce Flow?

No. FlitStack AI migrates data and schema only — Clio's legal-specific automations (intake workflows, conflict check sequences, matter milestone reminders, billing automation rules) do not transfer to Salesforce. They must be rebuilt in Salesforce Flow or Apex. We export your Clio workflow definitions as JSON reference files that your Salesforce admin can use as a rebuild specification. Workflow rebuild is a separate scoping item from the data migration.

What happens to Clio billing and trust accounting in Salesforce?

Clio bills, invoices, and trust ledger entries migrate to custom objects (Clio_Billing__c, Clio_Trust_Ledger__c) that preserve the financial data without creating a native billing system. The trust running balance must be calculated by summing transaction records. Salesforce has no native billing, trust accounting, or invoicing — these custom objects store the history; your admin must decide whether to connect them to an ERP integration post-migration for live billing workflows.

Can I migrate Clio custom fields to Salesforce custom fields?

Yes. Clio custom fields map to Salesforce custom fields using the __c suffix on the target object. Field types translate: text fields to Text(255), numbers to Number, dates to Date, dropdowns to Picklist, and long text to Long Text Area. Your Salesforce admin must create the custom fields in Object Manager before migration — we provide the exact field name, type, and pick-list value mapping as part of the migration specification.

What does a Clio matter become in Salesforce — a Case or an Opportunity?

The mapping depends on your firm's workflow priorities. Mapping to Salesforce Case gives you native case management features (SLA tracking, entitlements, case teams) but limits pipeline visibility. Mapping to Opportunity gives you Salesforce's forecasting, pipeline, and sales process features but loses case management. We support mixed mapping — some matter types route to Case, others to Opportunity — using a practice_area or matter_type discriminator field that your admin creates before migration.

Does the migration affect my Clio account during the cutover?

No. FlitStack AI uses scoped read access on Clio — your team continues working in Clio throughout the migration. The delta-pickup window (24–48 hours after initial load) captures any matters, time entries, or documents created or modified during the cutover so Salesforce reflects Clio's final state at go‑live. No write operations occur in Clio during extraction. We also provide a pre‑migration checklist to ensure your Clio data is export‑ready.

Will my Clio client portal document access work in Salesforce?

Documents and files migrate to Salesforce Files (ContentVersion/ContentDocument) attached to Cases. However, external client access to documents requires Salesforce Experience Cloud licenses and a configured customer portal — this is not part of a standard data migration. We migrate the document content and file-to-matter relationships; portal reconfiguration is a separate implementation step that your admin can scope after go-live. Consider reviewing the Experience Cloud setup guide to plan portal permissions and branding.

How does Clio's rate hierarchy translate to Salesforce?

Clio resolves rates through a hierarchy (custom rate → fixed rate → matter rate → client rate → user default) at the time of time entry creation. Salesforce has no native rate hierarchy — rates are static values. We preserve the full hierarchy structure as a JSON export and migrate effective rates at migration time as custom fields on Contact and Case. Your admin decides whether to rebuild rate logic in Salesforce Flow or accept static rate fields for reporting.

Get a quote

Moving from Clio to Salesforce?

Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.

Get a quote