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

Data migration route

Intapp to Litify migration

Intapp is a cloud specialist tool, and Litify is a cloud case management system. The records line up case for case, and the detail is in the fields and stages.

FromIntappCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Tasks: Carried across
  5. Time and expenses: Carried across
  6. Intake: Carried across
  7. Billing: Carried with mapping
  8. Custom fields: Carried with mapping
  9. Emails: Confirmed in the analysis
  10. Notes: Confirmed in the analysis
  11. Calendar: Confirmed in the analysis
  12. Templates: Confirmed in the analysis
ToLitifyCloud
  • 6 carried
  • 2 mapped
  • 4 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Intapp to Litify

Each row is a kind of record Intapp holds, whether Litify has a place for it, and what is planned. On this route six kinds of record carry across, two kinds need mapping and four kinds are confirmed in the analysis.

Records in Intapp and their place in Litify
RecordIn IntappIn LitifyWhat 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 placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeld in partClient, engagement and relationship data in Conflicts and DealCloud.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeld in partClient guideline documents and vendor agreements in Intapp Terms.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeCalendar events on the matter.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 placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldIntapp Time captures time across devices.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeld in partBillstream manages proforma review and approval.Has a place in partBilling is part of the product. Loading past invoices is scoped in the analysis.Carried with mapping
Custom fieldsFields and record types the firm added itselfHeldIntake request forms and workflows are built by each firm.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt in Litify’s document generation.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesHeldIntapp Intake runs client and matter onboarding; DealCloud holds pipeline.Has a placeLoaded as intakes.Carried across

What the plans mean

Carried across
Litify has a place for this kind of record. It is loaded there and checked against Intapp.
Carried with mapping
Litify 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.

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

Case to case, field by field.

Two case management systems look alike from a distance and differ in almost every detail. Each has its own idea of a case type, a stage, a party role and a deadline. Intapp and Litify may both hold a limitation date, yet one calculates it and the other stores what was typed. The mapping goes field by field and status by status, and the trial load is checked by opening real cases in both systems side by side.

Custom fields hold most of what the firm has built up. Years of intake answers, injury details or visa histories sit in fields the firm added itself. Each is matched to a field in Litify, and anything unmatched is kept as a note on the case so that it can still be searched. Workflows and document templates are rebuilt in the new system’s own tools. Open tasks come across with their owners and due dates.

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 Litify 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

Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.

  1. The design comes first

    Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.

  2. One party, many roles

    Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.

  3. Open enquiries load as intakes

    Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.

  4. Documents load after records

    Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.

  5. Validation rules reject bad rows

    A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.

More about moving into Litify

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Litify says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Intapp and checking each trial against Intapp.

  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 Litify. 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 Litify 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 Litify 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 toLitify

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

Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.

A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.

Set-up decisions in Litify

  • Define intake questionnaires and the rules for conversion
  • Set case types, matter stages and page layouts
  • Build matter plans that create tasks at each stage
  • Design document folders and generation templates per case type
  • Configure user roles and sharing for restricted matters
  • Decide on timekeeping, billing and accounting integrations

Questions

Intapp to Litify: 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 Litify?

In part. Billing is part of the product. Loading past invoices is scoped in the analysis. Open items are matched to what Litify can hold, and the rest of the billing history is kept as reports that open without Intapp.

Does everything in Intapp have a place in Litify?

Most of it does on paper. Emails, notes, calendar entries and templates could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Litify is kept as a readable archive, and you see which before the move.

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

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 Litify are the names and marks of their owners, used here only to identify the two systems.

Moving from Intapp to Litify?

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

We reply within one business day.