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

Data migration route

PracticeEvolve to Server drives migration

PracticeEvolve is a cloud 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.

FromPracticeEvolveCloud
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Templates: Carried with mapping
  4. Notes: 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. Tasks: Kept as a readable archive
  5. Time and expenses: Kept as a readable archive
  6. Billing: Kept as a readable archive
  7. Trust money: Kept as a readable archive
  8. Firm accounts: Kept as a readable archive
  9. Custom fields: Kept as a readable archive
  10. Intake: Kept as a readable archive
Readable archiveNo place in Server drives
  • 1 carried
  • 2 mapped
  • 1 to confirm
  • 10 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from PracticeEvolve to Server drives

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

Records in PracticeEvolve and their place in Server drives
RecordIn PracticeEvolveIn Server drivesWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldNo placeA matter becomes a folder; its details survive only in an index file.Kept as a readable archive
ContactsClients, other parties and referrersHeldIncludes a conflict search across the system.No placeCan be kept only as an exported spreadsheet.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeldIndexed for searching, including image-based PDFs.Has a placeFiles in folders, named and dated during the load.Carried across
EmailsEmails saved to matters or to the storeHeldMatter emails are filed and saved centrally.Has a place in partAs .msg or .eml files in each matter’s correspondence folder.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs a text or PDF file per matter, not as separate records.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partEvents are held on the matter.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTo-do lists, recurring tasks and workflows.No placeKept as a readable archive
Time and expensesTime and expense entries, billed and unbilledHeldAutomatic activity tracking converts to time entries.No placeOnly as exported reports or spreadsheets.Kept as a readable archive
BillingInvoices, payments and debtor balancesHeldFlexible billing with approval flows.Has a place in partInvoices as PDF files; no ledger.Kept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldClient funds management within the legal accounts.No placeOnly as exported ledger reports kept as files.Kept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldLegal accounts with balance sheet, debtors, cash flow and budget reporting.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeld in partEvolvePlus is described as fully customisable; the extent is confirmed in the analysis.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationHeldA supplied library of automated forms and precedents, plus the firm’s own.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 pipelinesHeldLead tracking for prospective clients.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 PracticeEvolve.
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 PracticeEvolve 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 PracticeEvolve 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 PracticeEvolve.

PracticeEvolve is hosted by its maker and Server drives sit on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What PracticeEvolve will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

PracticeEvolve keeps a firm’s data in the vendor’s Azure hosting, so extraction is arranged with the vendor. Which product the firm is on comes first, EvolveGo or EvolvePlus, because the two differ in how much has been customised. The accounts are inside the system, so client funds and office ledgers form part of every move.

  1. EvolveGo or EvolvePlus

    The vendor sells two cloud products. EvolveGo is the one built for quick implementation. EvolvePlus allows full customisation and workflows built without code. An EvolvePlus firm is likely to have fields, screens and processes of its own, and the analysis has to find them. An EvolveGo firm is closer to the product as supplied.

  2. Supplied precedents versus yours

    PracticeEvolve provides a large library of automated forms and precedents and keeps it up to date. Those belong to the vendor’s library. Precedents the firm added or adapted are the firm’s. We separate the two lists early, because only the second is rebuilt in the new system, and it is usually much shorter than staff expect.

  3. Where the documents are held

    Documents and filed emails are saved centrally and indexed for search. We confirm whether they are held by PracticeEvolve itself or by a separate document management product connected to it, as that decides who supplies the files and how each one is tied back to its matter.

  4. Messages in Communicate

    The built-in Communicate platform carries secure messages and shared files between the firm and its clients. Those conversations are part of the file for some matters. We check whether they are exported with the matter. If not, the messages for open matters are saved to the file as documents before cutover.

  5. Accounts in the same system

    Legal accounts, billing and client funds run inside PracticeEvolve, with its own reports for debtors, cash flow and budgets, and the UK site lists Making Tax Digital among its features. Leaving means choosing where office accounting goes next, and closing a tax period in the old system before balances are taken.

More about moving off PracticeEvolve

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 PracticeEvolve 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 PracticeEvolve: 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 PracticeEvolve, a final pass over a weekend picks up what changed since the trial. PracticeEvolve 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 PracticeEvolve 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 fromPracticeEvolve
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 PracticeEvolve 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

PracticeEvolve to Server drives: what firms ask

How do we get our data out of a hosted system?

Through the vendor, at the firm’s request. We specify what is needed: the database or a full export, every document with its matter reference, and closing accounts reports taken at the same time. How it is delivered is confirmed with PracticeEvolve during the analysis, and the first copy is tested before a cutover date is set.

Do the automated forms come with us?

The supplied forms stay with PracticeEvolve. Documents already produced from them are on the matters and move as files. The firm’s own precedents are exported and their merge fields replaced with the destination’s. If the new system has its own forms library, we compare it with the forms the firm uses most.

Is the Australian version different from the UK one?

The vendor publishes separate UK and Australian sites, and each edition follows its own country’s rules for client money and tax. Our method is the same for both. The checks on the financial cutover are written against the rules of the jurisdiction the firm practises in.

Do trust balances in PracticeEvolve 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 PracticeEvolve 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, tasks, time entries, billing records, trust ledgers, the firm’s accounts, custom fields and intake records. They are exported from PracticeEvolve 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 PracticeEvolve data is loaded into Server drives?

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

PracticeEvolve and Server drives are the names and marks of their owners, used here only to identify the two systems.

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