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

Data migration route

Docketwise to Server drives migration

Docketwise is a cloud case management system for immigration 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.

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

What moves

What moves from Docketwise to Server drives

Each row is a kind of record Docketwise 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, nine kinds have no place in Server drives and are archived and one kind is confirmed in the analysis.

Records in Docketwise and their place in Server drives
RecordIn DocketwiseIn Server drivesWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldImmigration matters with status, priority dates, expiry dates and receipt tracking.No placeA matter becomes a folder; its details survive only in an index file.Kept as a readable archive
ContactsClients, other parties and referrersHeldClients and the people related to their matters, plus leads.No placeCan be kept only as an exported spreadsheet.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeldKept against clients and matters; filing packages are assembled from forms and documents.Has a placeFiles in folders, named and dated during the load.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmail can be sent from inside the product; Gmail and Outlook are integrations.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 deadlinesHeldAppointments and deadlines; Google Calendar and Outlook are integrations.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTasks, with task and email automations.No placeKept as a readable archive
Time and expensesTime and expense entries, billed and unbilledHeldTime tracked against matters, alongside flat-fee charges.No placeOnly as exported reports or spreadsheets.Kept as a readable archive
BillingInvoices, payments and debtor balancesHeldInvoices, saved charges, payment plans and reminders; payments through LawPay.Has a place in partInvoices as PDF files; no ledger.Kept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldTrust requests, per-client balances and filing-fee disbursements.No placeOnly as exported ledger reports kept as files.Kept as a readable archive
Firm accountsGeneral ledger, office account and payablesTo be confirmedInvoices, payments and trust transactions sync to QuickBooks on some plans.No placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom attributes on contacts and matters.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationHeldGovernment form library, questionnaires and reusable email templates.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 pipelinesHeldLeads from the website, Facebook Messenger, WhatsApp and SMS in one dashboard.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 Docketwise.
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 Docketwise 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 Docketwise 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 Docketwise.

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

Where the data is now

Docketwise keeps one set of answers for each client and builds every form from it. A firm leaving has two different jobs. The practice records, meaning matters, time, invoices and trust, move much as they would from any system. The immigration records, meaning questionnaire answers, form data and case status tracking, only have a home if the destination is also built for immigration work.

  1. One questionnaire, many forms

    A single intake questionnaire can combine several immigration forms, and the client’s answers fill all of them. The answers are held as data against the client. In the analysis each answer is matched to a field in the new system. Where there is no match, the completed forms are kept as PDFs so the filed version is still on the matter.

  2. Trust is kept per client

    The product describes trust as per-client balances, with trust requests and filing-fee disbursements. Many practice systems hold trust per matter. A client with two open matters and one trust balance needs a rule for where the money sits after the move, and the firm sets that rule before the financial cutover is rehearsed.

  3. Flat fees and payment plans

    Immigration work is mostly billed as flat fees, and Docketwise handles that with saved charges and payment plans that debit the client through LawPay on a schedule. Part-paid plans are the awkward records. Each one is listed with what has been paid and what is still due, and the instalments are rebuilt in the new system.

  4. USCIS status tracking stops

    Receipt numbers are held on the matter and the product checks USCIS for status changes, then tells the client. The receipt numbers move as ordinary fields. The automatic checking does not, unless the new system does the same thing. Staff need to know before go-live who will be checking case status and how.

  5. Answers in other languages

    Clients can complete questionnaires in their own language, and messages can be translated. Some stored answers will therefore not be in English. The trial load is checked with a few of these clients in particular, because accented characters and non-Latin scripts are where an import most often damages text without anyone noticing.

More about moving off Docketwise

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

Docketwise to Server drives: what firms ask

What happens to our LawPay and QuickBooks connections?

LawPay and QuickBooks are separate products that Docketwise connects to, so they are not part of the move itself. Payment history stays in LawPay and the ledger stays in QuickBooks. What changes is the connection, which is set up again from the new system, with opening balances agreed between the two.

Can we keep the completed forms for every client?

Yes. A filed form is the record of what was sent to the government, so it is kept whatever the destination. Each one is saved as a PDF against the matter it belongs to, with its date. The trial load is checked by counting forms per matter against Docketwise for a sample of clients.

Do leads come across, or only clients?

Leads are held in the same system as clients, with their source and any messages. If the new system has an intake pipeline they can be loaded into it. Old leads that never became clients are often left out, and the firm chooses a cut-off date for those during the analysis.

Do trust balances in Docketwise 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 Docketwise 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, custom fields and intake records. They are exported from Docketwise 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 Docketwise data is loaded into Server drives?

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

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

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