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

Data migration route

Juris to Litify migration

Juris is a server-based accounting and billing system, and Litify is a cloud case management system. Only part of what Juris holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.

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

What moves

What moves from Juris to Litify

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

Records in Juris and their place in Litify
RecordIn JurisIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters as financial records, coded by lawyer, practice class and office.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeld in partClients, vendors and names typed on note cards.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeLoaded to the document component and attached to matters.Confirmed in the analysis
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 notesHeld in partNote cards at client or matter level.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partThe vendor’s site lists a Juris Calendar beside the main product.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldEntered in Juris, Juris Suite or the Juris Go mobile app.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldIncludes electronic billing.Has a place in partBilling is part of the product. Loading past invoices is scoped in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTo be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger with multi-level sub-accounts, payables and cheque reconciliation.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCustom fields are created before loading.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt in Litify’s document generation.Confirmed in the analysis

What the plans mean

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

Clients and jobs move. The books stay books.

An accounting or billing system and a case management system overlap less than firms expect. Juris knows clients, jobs, time and invoices. Litify knows cases, parties, documents and deadlines. The client list moves well, and jobs can seed the case list. Time and invoice history has a place only where the case system has a billing side, and the table above shows whether this one does. A general ledger does not belong in a case system.

So the plan has two halves. Records with a place in Litify are loaded and checked there. The rest is exported from Juris as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If Juris is staying as the accounting system, nothing financial needs to move at all, and the job is to line up client and case numbers so the two can be reconciled.

Juris runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Litify is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

Where the data is now

Juris holds the firm’s financial history and little else, so a move off it is mostly about money and the codes that classify it. Work in progress, receivables, trust, payables and the ledger are each agreed to a Juris report. Matter documents and calendars usually live in another product beside it, and that product is brought into the same plan.

  1. Three kinds of charge

    Juris separates fees, cash expenses and non-cash expenses, and supports accrual, billed and cash accounting methods. Many destinations know only time and disbursements. The mapping has to say where non-cash expenses go, or unbilled and billed cost totals will not agree after the load.

  2. Codes carry the reporting

    Billing lawyer, originating lawyer, working timekeeper, practice class, office and billing agreement are all coded on the matter. Partner reports are built on them. Each code table is extracted and mapped, and codes that have drifted into near-duplicates are tidied in Juris before extraction.

  3. Note cards feed conflict searches

    Clients and matters can have note cards with other names and special information, and the conflict search reads them. They are where related parties were typed when there was no better field. Note cards come across as notes, and names inside them are flagged in case the firm wants them as contacts.

  4. Juris Suite is a second layer

    Firms with Juris Suite enter time, run collections and keep budgets through it. Budgets and collection notes are extra records worth asking about. They are listed in the analysis so nobody finds after go-live that the collections history was never in scope.

  5. Sub-accounts in the chart

    The chart of accounts can be split into multi-level sub-accounts to match how the firm is organised. A destination with a flat chart needs those collapsed or turned into tracking categories. The firm’s accountant agrees the new chart first, and the closing trial balance is restated into it before loading.

More about moving off Juris

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 Juris and checking each trial against Juris.

  1. Analysis

    We read what Juris 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 Juris, 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 Juris: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Juris 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 Juris as at the cutover date. Juris 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 Juris 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 fromJuris
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 Juris 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

Juris to Litify: what firms ask

Can we keep our client and matter codes?

Juris codes are carried over wherever the destination allows a firm-set number, with the same padding and separators so old bills still match. If the new system numbers matters itself, the Juris code is stored as a reference and printed on invoices where clients expect to see it.

How much billing history should we bring?

Enough to answer a client’s question about a bill and to run aged debtors properly. Open invoices are loaded with their original dates. Paid invoices from earlier years can be loaded as summaries or left in Juris, kept read only. The destination’s limits usually decide it.

Our e-billing clients have strict formats. What happens?

The task codes, timekeeper classifications and client rates behind your e-bills are extracted and rebuilt in the new system. Past submissions stay where they are. Before go-live one real invoice for each e-billing client is produced from the trial load and checked against that client’s rules.

Do trust balances in Juris have a place in Litify?

That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Juris before the plan is fixed. If Litify turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

Does everything in Juris have a place in Litify?

Most of it does on paper. Documents, emails, notes, tasks, trust ledgers, the firm’s accounts, custom fields 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 Juris data is loaded into Litify?

Billing records are carried with mapping, so each mapping is agreed with you first. Documents, emails, notes, tasks, trust ledgers, the firm’s accounts, custom fields 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

Juris and Litify are the names and marks of their owners, used here only to identify the two systems.

Moving from Juris 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.