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

Data migration route

SmartAdvocate to Server drives migration

SmartAdvocate is a cloud case management system for personal injury work, 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.

FromSmartAdvocateCloud
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Notes: Carried with mapping
  4. Templates: Carried with mapping
  5. Trust money: Confirmed in the analysis
  6. Firm accounts: 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. Custom fields: 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 SmartAdvocate to Server drives

Each row is a kind of record SmartAdvocate 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 SmartAdvocate and their place in Server drives
RecordIn SmartAdvocateIn Server drivesWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases, with master and member cases for mass tort and class action work.No placeA matter becomes a folder; its details survive only in an index file.Kept as a readable archive
ContactsClients, other parties and referrersHeldNo placeCan be kept only as an exported spreadsheet.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeldDocuments page with categories, subcategories and custom folder views.Has a placeFiles in folders, named and dated during the load.Carried across
EmailsEmails saved to matters or to the storeHeldThe Outlook plugin attaches emails and their attachments to cases.Has a place in partAs .msg or .eml files in each matter’s correspondence folder.Carried with mapping
NotesFile notes, matter notes and contact notesHeldCase notes.Has a place in partAs a text or PDF file per matter, not as separate records.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldA Case Calendar and an Office Calendar. Critical deadlines sync to Outlook.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTasks created by WorkPlans and Automated Procedures.No placeKept as a readable archive
Time and expensesTime and expense entries, billed and unbilledHeldTime tracking, including from the mobile apps.No placeOnly as exported reports or spreadsheets.Kept as a readable archive
BillingInvoices, payments and debtor balancesHeld in partBuilt-in invoicing for hourly matters, from expenses and time entries.Has a place in partInvoices as PDF files; no ledger.Kept as a readable archive
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeOnly as exported ledger reports kept as files.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldDescribed as fully customisable, with custom merge codes and plaintiff fact sheets.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationHeldWord, Excel and PDF templates filled from thousands of merge codes.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 pipelinesHeldBuilt-in intake and lead management.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 SmartAdvocate.
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 SmartAdvocate 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 SmartAdvocate 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 SmartAdvocate.

SmartAdvocate 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 SmartAdvocate will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

SmartAdvocate holds a great deal of structured detail on each case, and leaving it is mostly a question of what the destination can receive. The edition matters for the mechanics. A Server firm has the database and document store on its own equipment. A Cloud firm arranges a copy through its hosted service. The content is the same either way.

  1. Server or Cloud edition

    With the Server edition the firm owns the installation, so a backup of the database and of the document and image storage can be taken on site. On the Cloud edition the vendor hosts both. Which edition the firm has is the first thing established, since it decides how the copy for the trial load is obtained.

  2. Master and member cases

    Mass tort and class action work is held as a master case with member cases related to it, and plaintiff fact sheets record the criteria for each litigation. Member cases are loaded as individual matters. The relationship and the fact sheet answers need an agreed home, or the firm loses the ability to report across a litigation.

  3. WorkPlans in progress

    A WorkPlan is a checklist that also automates steps, and Automated Procedures send reminders, texts, emails and generated documents. On an open case some items are done and some are pending. Pending items are loaded as tasks with due dates. The automation is rebuilt in the destination’s workflow tool from the WorkPlan definitions.

  4. Merge codes in templates

    Templates are Word, Excel or PDF files containing merge codes, including table codes that pull in lists of providers, bills, liens and expenses. The codes mean nothing outside SmartAdvocate. Template wording is kept and coded again for the new system, and list-style merges are tested early because not every system can produce them.

  5. Emails filed through Outlook

    The Outlook plugin files emails to the case and saves attachments to the documents page. Email is therefore part of the case record, and usually a large part. It is extracted with sender, recipients and date, and attachments already saved as documents are not loaded a second time.

More about moving off SmartAdvocate

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

SmartAdvocate to Server drives: what firms ask

Is SmartAdvocate cloud or on-premise?

Both exist. The Cloud edition is hosted by the vendor, and the Server edition is installed on the firm’s own server and maintained by the firm’s IT. Either way staff use it in a browser, and there are phone and tablet apps. A firm can tell which it has by who takes the backups.

Can our WorkPlans be migrated?

Yes for the open items, which load as tasks. The WorkPlan itself is SmartAdvocate automation and has to be recreated in the destination’s own workflow tool. Its definitions are documented step by step for that purpose, and the firm is asked which plans are still followed, because some will not have been touched in years.

We are moving to SmartAdvocate. What should we clean first?

Contacts and statuses. Duplicate providers and insurers multiply once they are attached to cases, and vague statuses cannot be translated to case stages. Merging the obvious duplicates and closing cases that are really finished, in the old system before extraction, costs far less than correcting them after the load.

Do trust balances in SmartAdvocate have a place in Server drives?

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 SmartAdvocate before the plan is fixed. If Server drives turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

What happens to records Server drives have no place for?

On this route that is matters, contacts, calendar entries, tasks, time entries, billing records, custom fields and intake records. They are exported from SmartAdvocate 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 SmartAdvocate data is loaded into Server drives?

Emails, notes and templates are carried with mapping, so each mapping is agreed with you first. Trust ledgers and the firm’s accounts 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

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

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