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

Data migration route

Google Drive data to SQLite

Google Drive is cloud file storage, and SQLite is a store of data kept as files the firm holds. What lands in SQLite is the register: every file’s name, place, dates and details, with the files themselves stored beside it.

FromGoogle DriveCloud
  1. Documents: Exported with mapping
  2. Emails: Exported with mapping
ToSQLiteFiles
  1. Templates: Kept as a readable archive
Readable archiveNo place in SQLite
  • 2 mapped
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Google Drive to SQLite

Each row is a kind of record Google Drive holds, whether SQLite has a place for it, and what is planned. On this route two kinds need mapping and one kind has no place in SQLite and is archived.

Records in Google Drive and their place in SQLite
RecordIn Google DriveIn SQLiteWhat is planned
DocumentsFiles stored in or linked from the systemHeldUploaded files plus Google Docs, Sheets and Slides, which are not files until exported.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 partOnly messages saved to Drive as files; mail itself is in Gmail.Has a place in partAs message files in folders, indexed in a table.Exported with mapping
TemplatesPrecedents, document templates and automationHeld in partPrecedents kept as files or as Google Docs that staff copy.No placePrecedent files are kept in folders, not in the database.Kept as a readable archive

What the plans mean

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.
Kept as a readable archive
SQLite has no place for it. It is exported in a format that opens without Google Drive 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

The files, and a register of what each one is.

A database is a poor place to keep documents and a good place to keep facts about them. On this route the files from Google Drive are exported to storage the firm controls, and SQLite receives the register: one row per file, with its path, size, dates, author and whatever profile or folder details existed. That register is what makes a large export searchable. It also proves completeness, since the row count and total size can be agreed to the source.

How useful the register is depends on how much Google Drive knows about each file. A document management system has a profile to carry. A plain folder has only a path and dates, and the client or matter has to be read out of folder names. Where versions or an audit history exist, each becomes a table of its own. The export is checked by picking documents at random in the source, finding them through SQLite, and opening the file to confirm it is the same one.

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

Where the data is now

Two things set a move off Google Drive apart from a move off any other drive. Much of the content is in Google’s own formats and has to be converted on the way out. And ownership is personal unless the firm used shared drives, so the files for one matter can be scattered across the accounts of everyone who ever worked on it.

  1. Docs, Sheets and Slides convert

    A Google Doc has no file behind it. On the way out it is saved as Word or PDF, a Sheet as Excel. The document’s revision history stays in Google, and links from one Doc to another still point back there. How layout, comments and suggestions come through is checked on a sample. The firm picks the output format per document type.

  2. My Drive files belong to people

    Every file in My Drive has one owner. A matter folder shared across the firm can contain files owned by six different accounts, some of them former staff. An administrator can transfer a user’s files to a new owner, and that is done for leavers before their accounts are touched.

  3. Shortcuts are not the file

    A shortcut in a matter folder points to a file stored somewhere else, often in another person’s drive. Copied naively it arrives as an empty pointer. Shortcuts are resolved to the real document during collection, and where the target can no longer be reached the gap is reported.

  4. Names Windows cannot hold

    Drive lets two files in one folder share a name, and Windows does not. Windows and SharePoint also refuse certain characters in names. Both are looked for in the analysis. Duplicated names are numbered and refused characters replaced by an agreed rule before loading, with the changes listed against the original names.

  5. Old versions of uploads expire

    For an uploaded file such as a PDF or Word document, Drive may delete an earlier version after 30 days or once there are 100 newer ones, unless someone marked it Keep forever. Earlier drafts the firm assumes are there may not be. What exists is counted in the analysis.

More about moving off Google Drive

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 Google Drive holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Google Drive 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 Google Drive: record counts, totals where Google Drive 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 Google Drive, the export is run a final time and checked again. There is nothing to go live. Google Drive 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 Google Drive 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 fromGoogle Drive
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 Google Drive 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

Google Drive to SQLite: what firms ask

What happens to our Google Docs when we move to a system that uses Word?

Each Doc is converted to a Word file, or to PDF where it is a finished document that should not change. Documents with heavy tables, drawings or linked Sheets are the ones checked by eye on a sample. The originals stay in Google, read only, until the firm is satisfied.

Some matter files are owned by people who have left. Are they lost?

Not if the account still exists, even suspended. A Workspace administrator can transfer its files to a current user, and that is done first. Where an account was deleted some time ago its My Drive files are gone, and the analysis will show the affected matters by the gaps in their folders.

Do we move Gmail and Calendar as well?

They are separate from Drive and are scoped separately. A firm can keep Google Workspace for mail and calendar and move only its matter files into a practice or document system. If emails need to sit on matters, the question is which mailboxes and labels are filed, and that is answered in the analysis.

Does the copy in SQLite hold documents from Google Drive?

In part. Listed in a table; the files themselves stay in folders beside the database. What SQLite can hold is written out once its mapping is agreed, and the rest is kept beside the data as files that open without Google Drive.

What happens to records SQLite has no place for?

On this route that is templates. They are exported from Google Drive 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 Google Drive is written out to SQLite?

Documents and emails are exported with mapping, so each mapping is agreed with you first. 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

Google Drive and SQLite are the names and marks of their owners, used here only to identify the two systems.

Moving from Google Drive 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.