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

Data migration route

Docketwise data to SQLite

Docketwise is a cloud case management system for immigration work, and SQLite is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what Docketwise holds and keeps it readable and open to queries.

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

What moves

What moves from Docketwise to SQLite

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

Records in Docketwise and their place in SQLite
RecordIn DocketwiseIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldImmigration matters with status, priority dates, expiry dates and receipt tracking.Has a placeA matters table keyed by matter number.Exported in full
ContactsClients, other parties and referrersHeldClients and the people related to their matters, plus leads.Has a placeContacts and their roles on matters as linked tables.Exported in full
DocumentsFiles stored in or linked from the systemHeldKept against clients and matters; filing packages are assembled from forms and documents.Has a place in partListed in a table; the files themselves stay in folders beside the database.Exported with mapping
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 message files in folders, indexed in a table.Exported with mapping
NotesFile notes, matter notes and contact notesHeldHas a placeA notes table linked to matters.Exported in full
CalendarAppointments, court dates and deadlinesHeldAppointments and deadlines; Google Calendar and Outlook are integrations.Has a placeA table of dated entries, with no calendar view.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldTasks, with task and email automations.Has a placeA table of tasks and their status at the final date.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldTime tracked against matters, alongside flat-fee charges.Has a placeA table of time and expense entries.Exported in full
BillingInvoices, payments and debtor balancesHeldInvoices, saved charges, payment plans and reminders; payments through LawPay.Has a placeInvoice and receipt tables; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeldTrust requests, per-client balances and filing-fee disbursements.Has a placeTrust transactions as rows, for look-up and not for accounting.Exported in full
Firm accountsGeneral ledger, office account and payablesTo be confirmedInvoices, payments and trust transactions sync to QuickBooks on some plans.Has a placeLedger journals as rows, where the source held them.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom attributes on contacts and matters.Has a placeColumns added to the table they belonged to.Exported with mapping
TemplatesPrecedents, document templates and automationHeldGovernment form library, questionnaires and reusable email templates.No placePrecedent files are kept in folders, not in the database.Kept as a readable archive
IntakeLeads, enquiries, intake forms and pipelinesHeldLeads from the website, Facebook Messenger, WhatsApp and SMS in one dashboard.Has a placeAn enquiries table, where the source tracked them.Exported in full

What the plans mean

Exported in full
SQLite has a place for this kind of record. It is loaded there and checked against Docketwise.
Exported with mapping
SQLite 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
SQLite 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

Not a new system. A complete copy the firm can query.

Writing Docketwise out to SQLite is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Docketwise as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

Docketwise is hosted by its maker and SQLite sits 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

A SQLite archive suits a firm that wants the old system’s records kept, seldom consulted, and free of any server or subscription. Everything structured goes into one file. That simplicity moves the responsibility elsewhere: the file has no security of its own and no administrator watching it, so where it is stored and who can reach it are the real decisions.

  1. One file, kept with the archive

    Matters, contacts, time, invoices and trust transactions become tables in a single file. It is stored with the firm’s closed-matter records and can be copied like any document. A checksum recorded when the file is finalised lets anyone confirm, years later, that the copy they hold has not been altered, and the firm decides whether to keep one.

  2. No logins inside the file

    SQLite has no users or passwords. Anyone who can open the file can read every client’s ledger. Protection comes from where it is kept, such as a restricted folder or an encrypted volume, and that choice is the firm’s. It can suit an archive consulted by two people, and it is said plainly so nobody assumes otherwise.

  3. Built for reading, not sharing

    Only one program can write to the file at a time, and SQLite’s authors point people to a client/server database where many users share data over a network. A finished archive never meets that limit. It is the reason SQLite is used here for records that are closed and not for anything staff still update.

  4. Documents stay outside it

    Documents remain ordinary files in matter folders, and a table in the database lists each one with its matter, title, dates and path. Keeping them as files means they open with a double-click and can be handed to a client. The table is how a file is found by matter number instead of by guessing its name.

  5. Someone has to open it

    SQLite publishes its own command-line program for opening a database file, and other tools read the format too. None of that helps if nobody remembers how. Saved queries for the usual look-ups and a short note on which tool to use can sit in the same folder as the file, and the firm decides what it needs.

More about moving into SQLite

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what Docketwise holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Docketwise holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to SQLite as a trial and checked against Docketwise: record counts, totals where Docketwise holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in Docketwise, the export is run a final time and checked again. There is nothing to go live. Docketwise is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

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 toSQLite

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 SQLite. 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

SQLite is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

There is nothing to install on a server and nothing to license. The work is in making the file usable and safe to keep: naming it, documenting its tables, storing it where the firm’s records policy says archives go, and checking that a member of staff can open it and find a matter. Whether a second copy is held somewhere separate is the firm’s call.

What is agreed and set up

  • File name, storage location and whether a second copy exists
  • Whether a checksum is recorded for later verification
  • Saved queries for matter, ledger and document look-ups
  • Which tool staff will use to open the file
  • Who may open the folder the file sits in
  • Retention period and destruction date noted beside the file

Questions

Docketwise to SQLite: 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.

Does the copy in SQLite hold trust ledgers from Docketwise?

Yes. Trust transactions as rows, for look-up and not for accounting. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Docketwise as at the export date.

What happens to records SQLite has no place for?

On this route that is templates. 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 is written out to SQLite?

Documents, emails and custom fields are exported with mapping, so each mapping is agreed with you first. The firm’s accounts are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.

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

Moving from Docketwise to SQLite?

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

We reply within one business day.