Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

Intapp to Clio Manage migration

Intapp is a cloud specialist tool, and Clio Manage is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in Clio Manage, often from a separate accounts package.

FromIntappCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Tasks: Carried across
  5. Time and expenses: Carried with mapping
  6. Billing: Carried with mapping
  7. Custom fields: Carried with mapping
  8. Emails: Confirmed in the analysis
  9. Notes: Confirmed in the analysis
  10. Calendar: Confirmed in the analysis
  11. Templates: Confirmed in the analysis
ToClio ManageCloud
  1. Intake: Kept as a readable archive
Readable archiveNo place in Clio Manage
  • 4 carried
  • 3 mapped
  • 4 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Intapp to Clio Manage

Each row is a kind of record Intapp holds, whether Clio Manage has a place for it, and what is planned. On this route four kinds of record carry across, three kinds need mapping, one kind has no place in Clio Manage and is archived and four kinds are confirmed in the analysis.

Records in Intapp and their place in Clio Manage
RecordIn IntappIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partNew business requests and their approvals, by client and matter.Has a placeImported from a matters template, after contacts.Carried across
ContactsClients, other parties and referrersHeld in partClient, engagement and relationship data in Conflicts and DealCloud.Has a placePeople and companies, with related contacts linked to matters by a separate template.Carried across
DocumentsFiles stored in or linked from the systemHeld in partClient guideline documents and vendor agreements in Intapp Terms.Has a placeFiled under the matter; Clio scopes document migration separately from data.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeHeld as communications on the matter, with phone logs.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeMatter notes and contact notes each have a template.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeCalendar events have a migration template.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partApproval workflows, tasks and alerts tied to intake and client terms.Has a placeTasks have a migration template.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldIntapp Time captures time across devices.Has a place in partUnbilled time entries load; billed time entries do not, by Clio’s migration guide.Carried with mapping
BillingInvoices, payments and debtor balancesHeld in partBillstream manages proforma review and approval.Has a place in partAn outstanding balance loads as one line per matter; past invoices do not.Carried with mapping
Custom fieldsFields and record types the firm added itselfHeldIntake request forms and workflows are built by each firm.Has a placeCreated first, then filled from the custom field templates.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a placeRebuilt as Clio document templates with its merge fields.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesHeldIntapp Intake runs client and matter onboarding; DealCloud holds pipeline.No placeLeads and intake forms belong in Clio Grow.Kept as a readable archive

What the plans mean

Carried across
Clio Manage has a place for this kind of record. It is loaded there and checked against Intapp.
Carried with mapping
Clio Manage holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
Confirmed in the analysis
We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.
Kept as a readable archive
Clio Manage has no place for it. It is exported in a format that opens without Intapp and handed to the firm as a read-only archive.

The table states what the two products hold and what NewLaw plans for. It is not a promise that every record moves: that is settled against your own data in the analysis.

This kind of move

Cases come across. The accounts are set up new.

A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to Clio Manage brings those two sources together. The case records come from Intapp. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.

Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in Clio Manage, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Intapp depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Intapp is kept running until the checks on Clio Manage are finished.

Where the data is now

Nobody moves off Intapp as a whole. A firm replaces one product, or changes its practice system and finds that the Intapp products were fed by it. Either way the work starts by listing which products are licensed, what each holds that exists nowhere else, and which records are only copies of data owned by the finance system.

  1. Name the product first

    Intake, Conflicts, Walls, Terms, Time, Billstream and DealCloud each keep different records. A plan to move from Intapp means little until the product is named. The analysis opens with the list of products in use and whether each is on Intapp’s cloud or an earlier installation in the firm’s own environment.

  2. Intake history

    The Intake product holds each new business request with its answers, risk assessment and approvals. That is the firm’s evidence that a matter was opened properly. A practice system may take the client and matter but has no place for the approval trail, which is then kept as a document on the matter or in an archive.

  3. Conflict search records

    Conflicts brings client, engagement and relationship data together for searching and records the clearance of each search. The underlying names come from other systems and move with them. Clearance records do not, and the firm’s risk team decides how long it must stay retrievable and in what form.

  4. Time before it is posted

    The Time product captures time on phones and desktops and hands entries to the billing system. Entries still in draft, or captured but not released, may exist nowhere else. A cut-off is agreed so every timekeeper releases their time before the switch, and a count of unreleased entries is taken on the day.

  5. Walls and who sees what

    Walls sets information barriers once and enforces them across the firm’s other systems. When one of those systems is replaced, the restrictions have to be applied to the new one before any matter is opened to staff. The list of walled matters and their permitted teams is taken out early for that reason.

More about moving off Intapp

Where it is going

Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.

  1. Matters link by client name

    The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.

  2. Decide the numbering scheme first

    Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.

  3. Balances, one line each

    Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.

  4. Custom fields must exist

    Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.

  5. Rates and permissions by hand

    Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.

More about moving into Clio Manage

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  1. Analysis

    We read what Intapp holds and how its records link, then agree with you, field by field, where each piece will sit in Clio Manage. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Intapp, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Clio Manage as a trial and checked against Intapp: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Intapp are frozen for an agreed window, the data is collected a final time and Clio Manage goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in Intapp as at the cutover date. Intapp is kept read only as the fall-back record.

Fixed price, agreed after the analysis. How NewLaw moves legal data

Start

Start this migration

Tell us what is in Intapp and roughly how much of it. The first step is the analysis, and the price is fixed once it is done.

Step 1 of 5

Step 1 of 5: Start with the route

Moving fromIntapp
Moving toClio Manage

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what Intapp holds

    What is in it, how its records link, and where each piece would sit in Clio Manage. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. A fixed price in writing

    Set after the analysis, so it reflects what is in your data. You have it before any work starts.

Beyond the data

Setting up Clio Manage

Loaded data is not yet a working system. This is what NewLaw sets up in Clio Manage, beyond the migration, so that people can work in it from the first day.

Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.

Set-up decisions in Clio Manage

  • Matter numbering scheme, practice areas and matter stages
  • Custom fields for matters and contacts, by practice area
  • Document templates with merge fields, uploaded from Word or PDF
  • Billing settings, user and client rates, and trust accounts
  • Roles and permissions for each user
  • Outlook add-in, Clio Drive and the accounting connection

Questions

Intapp to Clio Manage: what firms ask

We are changing practice management system. What happens to our Intapp products?

They stay, but their connections change. Intake, Conflicts and Time work from the clients, matters and timekeepers in the practice system and write back to it. Each of those feeds is rebuilt against the new system and tested during the trial load, so new matters and time entries have a working route before go-live.

Can Intapp Time entries be moved into a practice system?

Released time normally already sits in the firm’s billing system, so it moves with that system. What needs attention is time still held in the capture tool. Timekeepers release it before the cut-off, and anything left is exported and loaded as unbilled entries against the right matters.

Is DealCloud covered?

DealCloud is Intapp’s relationship management product, used for contacts, pipeline and marketing. Moving it is a CRM migration in its own right. Contacts and their history are mapped to the new CRM or to the practice system’s contact records, and duplicates between the two lists are merged where they can be identified.

Does billing history from Intapp move into Clio Manage?

In part. An outstanding balance loads as one line per matter; past invoices do not. Open items are matched to what Clio Manage can hold, and the rest of the billing history is kept as reports that open without Intapp.

What happens to records Clio Manage has no place for?

On this route that is intake records. They are exported from Intapp in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

What has to be decided before Intapp data is loaded into Clio Manage?

Time entries, billing records and custom fields are carried with mapping, so each mapping is agreed with you first. Emails, notes, calendar entries and templates are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.

Where to start

Before and after the move.

Choosing the system comes before a migration. Setting it up and putting AI to work come after.

How we do itDiscovery to rollout, step by step

Intapp and Clio Manage are the names and marks of their owners, used here only to identify the two systems.

Moving from Intapp to Clio Manage?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.