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

Data migration route

PerfectLaw to SimpleLaw migration

PerfectLaw is a server-based practice management system, and SimpleLaw is a cloud one. Both run a whole practice, so this is a full move, and the financial records set the timetable.

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

What moves

What moves from PerfectLaw to SimpleLaw

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

Records in PerfectLaw and their place in SimpleLaw
RecordIn PerfectLawIn SimpleLawWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases are managed in AIM, the Attorney’s Information Manager.Has a placeCarried across
ContactsClients, other parties and referrersHeldParties are related to matters by defined relationships for conflict checks.Has a placeAs leads, clients or other contacts in the CRM.Carried across
DocumentsFiles stored in or linked from the systemHeldIts own document management system; reports can be profiled into it.Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmail profiling tools are listed among its applications.To be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesHeldHas a placeCarried across
CalendarAppointments, court dates and deadlinesHeldCalendars and dockets.Has a placeCarried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime, cost and expense entry.Has a placeCarried across
BillingInvoices, payments and debtor balancesHeldIncludes collections and billing compliance tools.Has a place in partInvoices are created in the product; loading invoice history is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTrust history by matter within client, for each trust account.Has a place in partTrust balances are supported; history depth is confirmed in the analysis.Carried with mapping
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger and accounts payable, with profit centres.No placeGeneral ledger stays in QuickBooks or another accounting package.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeldForms and document assembly.Has a place in partTemplates are rebuilt using SimpleLaw’s own automation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partA matter intake workflow for opening new matters.Has a placeLeads and intake forms.Carried across

What the plans mean

Carried across
SimpleLaw has a place for this kind of record. It is loaded there and checked against PerfectLaw.
Carried with mapping
SimpleLaw 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
SimpleLaw has no place for it. It is exported in a format that opens without PerfectLaw 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

The whole practice moves, accounts included.

A move between two practice management systems is the widest kind there is. PerfectLaw and SimpleLaw each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.

The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with PerfectLaw’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.

PerfectLaw 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. SimpleLaw 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

PerfectLaw is one database doing the work of four or five products. A firm leaving it is replacing its case management, document store, billing, general ledger and accounts payable at once, often with two or three separate systems. The plan has to say which destination takes which part, and how the links between them, especially client and matter numbers, are kept.

  1. One source, several destinations

    Front office and back office share a database. If the firm is moving to a practice management system plus a separate accounting package, the single source is split in two. Client and matter identifiers must be identical in both destinations, so they are fixed first and every extract is keyed on them.

  2. Matter within client

    Trust history is kept by matter within client, and the rest of the system follows the same client and matter structure. A destination that numbers matters independently of clients needs a rule for combining the two. We settle that rule with the accounts team, since their reports and bank records use the existing numbers.

  3. Scanned invoices and cheques

    The accounts payable side can store scanned supplier invoices and images of signed cheques, linked to vendors, matters and clients. These are financial records, not matter documents. They are counted separately and usually go to the accounting package or a finance archive, with the link to the vendor kept in the file name or index.

  4. Records management by barcode

    PerfectLaw lists records management with barcodes among its front office applications, for tracking physical files. If the firm uses it and the new system has no records module, the file locations are loaded into custom fields on the matter or handed to the records team as a register.

  5. A segmented general ledger

    The general ledger uses multi-segment account numbers and can distribute overhead among profit centres. An accounting package with a flat chart of accounts needs those segments translated into its own tracking categories or classes. The firm’s accountant agrees the new chart before opening balances are prepared.

More about moving off PerfectLaw

Where it is going

Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.

  1. Lead, client or contact

    A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.

  2. Billing type on each matter

    Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.

  3. Storage chosen before loading

    If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.

  4. Custom fields named for templates

    Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.

  5. Portal access client by client

    The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.

More about moving into SimpleLaw

How NewLaw runs it

Four steps, in this order.

Trust money moves on this route, so the trust cutover gets a rehearsal of its own.

  1. Analysis

    We read what PerfectLaw holds and how its records link, then agree with you, field by field, where each piece will sit in SimpleLaw. 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 PerfectLaw, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into SimpleLaw as a trial and checked against PerfectLaw: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in PerfectLaw are frozen for an agreed window, the data is collected a final time and SimpleLaw goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. PerfectLaw 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 PerfectLaw 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 fromPerfectLaw
Moving toSimpleLaw

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 PerfectLaw holds

    What is in it, how its records link, and where each piece would sit in SimpleLaw. 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 SimpleLaw

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

The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.

Set-up decisions in SimpleLaw

  • Labels for documents, activities, expenses and contact IDs
  • Custom fields and intake forms for each practice area
  • Document templates and the attorney-client agreement
  • Workflows for case types that follow a standard process
  • User permission sets and client portal visibility
  • QuickBooks connection and the online payment processor

Questions

PerfectLaw to SimpleLaw: what firms ask

Can everything in PerfectLaw go into one new system?

Sometimes, if the destination includes full accounting. More often the firm ends up with a practice management system and an accounting package, and perhaps a document management system. The analysis lists every PerfectLaw function the firm uses and shows which destination covers it, so nothing is assumed.

What happens to documents in the PerfectLaw DMS?

They are extracted with whatever profile data the document store keeps for them, such as client and matter. In the destination each document is filed to its matter, into a folder derived from the profile where folders are used. Reports that were profiled into the document store are identified, since most are not matter documents.

We are in PerfectLaw’s hosted cloud. Does that change anything?

It changes who provides the copy. A firm with its own server gives us access with its IT provider. A firm in the vendor’s hosted environment asks the vendor for the database and documents. The checks afterwards are the same, and a read-only copy still needs a home once hosting ends.

Do trust balances in PerfectLaw have a place in SimpleLaw?

In part. Trust balances are supported; history depth is confirmed in the analysis. The analysis sets out which trust records have a place in SimpleLaw and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

What happens to records SimpleLaw has no place for?

On this route that is the firm’s accounts. They are exported from PerfectLaw 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 PerfectLaw data is loaded into SimpleLaw?

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

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

Moving from PerfectLaw to SimpleLaw?

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

We reply within one business day.