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

Data migration route

SimpleLaw to Litify migration

SimpleLaw is a cloud practice management system, and Litify is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.

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

What moves

What moves from SimpleLaw to Litify

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

Records in SimpleLaw and their place in Litify
RecordIn SimpleLawIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldThe vendor uses matter and case interchangeably.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldLeads, clients and other contacts in one CRM.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeldStored on SimpleLaw’s servers or in the firm’s Dropbox, Google Drive or OneDrive.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails sent from within SimpleLaw through Google or Outlook are tracked by matter.Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesHeldClients can also add notes through the portal.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldAppointments by firm member or type, synced with Google or Outlook.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldWorkflows create tasks, appointments and documents for standard case types.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldOne timer per matter, plus manual entries.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldHourly, flat fee, instalment, contingency, pro bono and LEDES invoices.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 balancesHeld in partTrust billing and initial trust payments are supported; ledger detail was not confirmed.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom fields feed intake forms, reports and document automation.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeldReusable templates filled from stored data and intake answers.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldWebsite forms, custom intake forms and lead tracking in the CRM.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 SimpleLaw.
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

Matters become cases. The ledgers need a home.

Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Litify. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.

Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from SimpleLaw has to be given a case type in Litify, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Litify is exported as reports and ledgers the firm can open without SimpleLaw, and kept as the record of what was billed and held.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of SimpleLaw 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 SimpleLaw is kept running until the checks on Litify are finished.

Where the data is now

SimpleLaw lets a firm rename and rearrange a good deal, so the first step in leaving it is learning this firm’s version: what it calls its record types, where it chose to store files and which clients were given portal access. With that understood the move itself is usually modest in size, since the product is sold to solo lawyers and small firms.

  1. Files in your drive or theirs

    A firm chooses whether documents sit on SimpleLaw’s servers or in its own Dropbox, Google Drive or OneDrive. In the second case the files already belong to the firm and need no extraction. What has to be preserved is the record of which folder belongs to which matter.

  2. The firm’s own labels

    Documents, activities, expenses and contact IDs can all be renamed to suit the firm. Staff describe their records in those terms, and screens and reports follow them. A short glossary is written first, so that something the firm calls a Disbursement or a File Ref is mapped to the right field in the destination.

  3. What clients added

    Through the portal, clients upload documents, add notes, complete intake forms and message the legal team. Client-written notes sit among the firm’s own. They are marked with their author on the way out, so that in the new system nobody mistakes a client’s comment for a lawyer’s file note.

  4. Referred and co-counsel matters

    Matters referred or shared with co-counsel through the SimpleLaw network are visible to both firms inside the platform. That shared view does not exist elsewhere. The other lawyer is recorded as a contact with a role on the matter, and the firm tells co-counsel how documents will be exchanged afterwards.

  5. Payments recorded in two ways

    Clients may pay through an integrated processor, or the firm may manage payments offline or through QuickBooks. Where the second route was used, the payment record inside SimpleLaw may be incomplete. Receivables are checked against the bank statement or QuickBooks before any balance is carried forward to the new system.

More about moving off SimpleLaw

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

  1. Analysis

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

  4. Cutover

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

SimpleLaw to Litify: what firms ask

Does SimpleLaw replace our accounting software?

No. It records time, raises invoices and takes payments, and it can sync with QuickBooks. The general ledger, payroll and tax reporting stay in the accounting package. A firm moving to it from an all-in-one system should plan where its books will be kept before the practice data is moved.

Our documents are in Google Drive. Do they have to be uploaded?

Not necessarily. SimpleLaw offers Google Drive, Dropbox and OneDrive as storage options alongside its own servers. If the firm keeps Google Drive, the work is arranging folders so each matter finds its files. How the connection handles an existing folder tree is confirmed in the analysis.

We are leaving SimpleLaw. Can clients still reach their documents?

Only for as long as the SimpleLaw account and its portal remain active. Documents clients uploaded are extracted with the matter. If the new system has a client portal, access is set up again there, and clients are told in advance where to find their files from the cutover date.

Do trust balances in SimpleLaw 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 SimpleLaw 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 SimpleLaw have a place in Litify?

Most of it does on paper. Notes and trust ledgers 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 SimpleLaw data is loaded into Litify?

Emails, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes and trust ledgers 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

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

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