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

Data migration route

PerfectLaw to Server drives migration

PerfectLaw is a server-based practice management system, and Server drives are plain files on equipment the firm controls. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

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

What moves

What moves from PerfectLaw to Server drives

Each row is a kind of record PerfectLaw holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping, eight kinds have no place in Server drives and are archived and two kinds are confirmed in the analysis.

Records in PerfectLaw and their place in Server drives
RecordIn PerfectLawIn Server drivesWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases are managed in AIM, the Attorney’s Information Manager.No placeA matter becomes a folder; its details survive only in an index file.Kept as a readable archive
ContactsClients, other parties and referrersHeldParties are related to matters by defined relationships for conflict checks.No placeCan be kept only as an exported spreadsheet.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeldIts own document management system; reports can be profiled into it.Has a placeFiles in folders, named and dated during the load.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmail profiling tools are listed among its applications.Has a place in partAs .msg or .eml files in each matter’s correspondence folder.Carried with mapping
NotesFile notes, matter notes and contact notesHeldHas a place in partAs a text or PDF file per matter, not as separate records.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldCalendars and dockets.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleTo be confirmedNo placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime, cost and expense entry.No placeOnly as exported reports or spreadsheets.Kept as a readable archive
BillingInvoices, payments and debtor balancesHeldIncludes collections and billing compliance tools.Has a place in partInvoices as PDF files; no ledger.Kept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldTrust history by matter within client, for each trust account.No placeOnly as exported ledger reports kept as files.Kept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger and accounts payable, with profit centres.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedNo placeConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeldForms and document assembly.Has a place in partPrecedents as Word files; merge fields tied to the old system stop working.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partA matter intake workflow for opening new matters.No placeKept as a readable archive

What the plans mean

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

Out of the system, into folders the firm can read.

File storage has folders and files and nothing else. Moving from PerfectLaw into Server drives means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Server drives do not allow in a name.

Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in PerfectLaw.

Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in PerfectLaw stays untouched until the copy in Server drives has been checked.

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

Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.

  1. Agree the tree and the names

    A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.

  2. Budget the path length

    Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.

  3. Dates have to be set deliberately

    A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.

  4. Emails become message files

    Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.

  5. Keep an index beside the files

    A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.

More about moving into Server drives

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Server drives on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what PerfectLaw holds and how it is organised, then agree with you where each kind of record will sit in Server drives. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into Server drives and checked against PerfectLaw: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in PerfectLaw, a final pass over a weekend picks up what changed since the trial. 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 toServer drives

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 Server drives. 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

Structure, permissions and handover

Server drives are storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.

What is agreed and set up

  • Share and top-level folders for clients, precedents and administration
  • Security groups and folder permissions, with restricted matters separate
  • Drive letter mapped for every user at sign-in
  • Backup schedule and shadow copies for earlier versions
  • Written naming rule for client, matter and document names
  • Read-only area for closed matters and archived system exports

Questions

PerfectLaw to Server drives: 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 Server drives?

No. Server drives do not keep trust ledgers. Only as exported ledger reports kept as files. Trust records from PerfectLaw are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.

What happens to records Server drives have no place for?

On this route that is matters, contacts, calendar entries, time entries, billing records, trust ledgers, the firm’s accounts and intake records. 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 Server drives?

Emails, notes and templates are carried with mapping, so each mapping is agreed with you first. Tasks and custom fields are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

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

Moving from PerfectLaw to Server drives?

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

We reply within one business day.