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

Data migration route

Harvest to Google Drive migration

Harvest is a cloud accounting and billing system, and Google Drive is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.

FromHarvestCloud
  1. Notes: Carried with mapping
  2. Documents: Confirmed in the analysis
  3. Custom fields: Confirmed in the analysis
  4. Templates: Confirmed in the analysis
ToGoogle DriveCloud
  1. Matters: Kept as a readable archive
  2. Contacts: Kept as a readable archive
  3. Tasks: Kept as a readable archive
  4. Time and expenses: Kept as a readable archive
  5. Billing: Kept as a readable archive
Readable archiveNo place in Google Drive
  • 1 mapped
  • 3 to confirm
  • 5 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Harvest to Google Drive

Each row is a kind of record Harvest holds, whether Google Drive has a place for it, and what is planned. On this route one kind needs mapping, five kinds have no place in Google Drive and are archived and three kinds are confirmed in the analysis.

Records in Harvest and their place in Google Drive
RecordIn HarvestIn Google DriveWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partProjects under clients stand in for matters; there are three project types.No placeA matter is a folder inside a shared drive.Kept as a readable archive
ContactsClients, other parties and referrersHeld in partClients and client contacts, kept mainly as invoice recipients.No placeContacts belong in Google Contacts, not Drive.Kept as a readable archive
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeAny file type, stored as uploaded or converted to Google formats.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeld in partFree-text notes on each time entry.Has a place in partAs a Doc or Word file in the matter’s folder.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeld in partTasks are categories of work for time entries, not to-dos.No placeKept as a readable archive
Time and expensesTime and expense entries, billed and unbilledHeldTimers and timesheets by person, project and task, with approvals.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldInvoices and estimates, with online payment through Stripe or PayPal.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedNo placeConfirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedents load as files; the load does not rebuild Word automation in Docs.Confirmed in the analysis

What the plans mean

Carried with mapping
Google Drive 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
Google Drive has no place for it. It is exported in a format that opens without Harvest 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

An export the firm can open without the system.

Google Drive holds files, and most of what Harvest holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used Harvest, by client or by year, with a short index file saying what is where.

Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in Google Drive is limited before the export is copied in.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Harvest depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Harvest is kept running until the checks on Google Drive are finished.

Where the data is now

Harvest knows about clients, projects, tasks, people, time entries, expenses, invoices and estimates. It does not know about matters or trust money. A firm leaving it for a practice system is turning projects into matters and carrying across time and invoice history, while the firm’s books stay in the accounting package Harvest was feeding.

  1. Client, then project

    A Harvest client record holds a name, an address and a currency, with contacts added mainly so invoices reach the right person. The detail a legal system wants about a client, such as other parties or a responsible lawyer, was never recorded here and is gathered from elsewhere or added after loading.

  2. Tasks are not to-dos

    In Harvest a task is a category of work, such as drafting or attendance, that a time entry is logged against, and it can carry its own billable rate. Tasks map to activity codes in a practice system. They are not a list of things waiting to be done on a matter.

  3. Three ways to set rates

    A Time & Materials project bills at a project rate, a rate per person or a rate per task. The same lawyer can therefore have different rates on different projects. Historical time is loaded with the rate it was recorded at, and the going-forward rate table is built separately in the new system.

  4. Invoices copied to the ledger

    Where the QuickBooks Online or Xero integration is on, invoices and payments were copied across, but time and expenses went only as invoice lines. The accounting package holds the receivables and Harvest holds the time behind them. Both are read, and the invoice numbers are used to match one to the other.

  5. Archived clients and projects

    Clients and projects that are finished can be archived instead of deleted, and archived records are easy to leave out of an export. The analysis counts active and archived records separately, and the firm chooses whether closed work comes across as closed matters or stays behind in the Harvest account.

More about moving off Harvest

Where it is going

Putting a firm’s matter files into Google Drive means choosing shared drives over personal ones and then deciding how many shared drives there should be. That second decision is driven by Google’s limits and by who is allowed to see what, since access is granted mainly at the level of the whole shared drive.

  1. Shared drives, not My Drive

    Files loaded into a shared drive belong to the firm and remain when the person who loaded them leaves. Anything loaded into someone’s My Drive belongs to that person. Matter files therefore go to shared drives, and My Drive is left for personal working papers.

  2. One drive cannot hold everything

    Google caps a shared drive at 500,000 items, counting folders, shortcuts and anything in the trash, and at 100 levels of nested folders. A firm with twenty years of matters can pass the item cap in a single drive. The split is planned up front, commonly by practice group, or by open and closed matters.

  3. Membership is the main control

    Every member of a shared drive can see all of it unless a Manager restricts a particular folder. Matters that only certain people may open are simpler to protect in a shared drive of their own. The firm supplies the list of restricted matters and partners’ private folders before the drives are created.

  4. The daily upload limit

    Each user can upload 750 GB to Drive in 24 hours, and then has to wait. For a large document set that limit sets the shortest time the load can take. The total size is measured in the analysis, so the firm knows before the freeze whether its documents fit inside a weekend.

  5. Keep Office files as Office files

    Word and Excel files can be stored in Drive as they are or converted to Google formats. Unless the firm asks otherwise they are loaded unconverted, so court documents and automated precedents arrive as they left. The firm decides afterwards which templates are worth rebuilding as Google Docs.

More about moving into Google Drive

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Google Drive on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Harvest holds and how it is organised, then agree with you where each kind of record will sit in Google Drive. 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 Google Drive and checked against Harvest: 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 Harvest, a final pass over a weekend picks up what changed since the trial. Harvest 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 Harvest 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 fromHarvest
Moving toGoogle Drive

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 Harvest holds

    What is in it, how its records link, and where each piece would sit in Google Drive. 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

Google Drive is 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 Drive set-up for a law firm is a small number of deliberate choices made in the Workspace Admin console and then left alone. Which shared drives exist, who manages each, whether staff may share outside the firm, and whether people work from the browser or from Drive for desktop. Staff also need to be shown where a new matter folder goes.

What is agreed and set up

  • Shared drives by practice group, with a naming pattern
  • Managers and member access levels for each shared drive
  • External sharing rules set in the Admin console
  • Drive for desktop on PCs that need Explorer access
  • A standard subfolder set copied into every new matter
  • Transfer of leavers’ My Drive files as a standing procedure

Questions

Harvest to Google Drive: what firms ask

Harvest has projects, not matters. How does that convert?

Each project becomes a matter under the same client, keeping its name and any code as the matter reference. Firms that used one long-running project per client, with all work logged to it, decide during clean-up whether to split it into separate matters or carry it as a single general matter.

Will our old time entries keep their notes?

Time entries are read with their date, person, project, task, hours, billable flag and the notes typed on them. In the new system the notes become the narrative on each entry. Entries already invoiced are linked to their invoice where the destination supports that, and listed as billed where it does not.

We have no trust records in Harvest. Is that a problem?

It is common. Harvest has no trust accounting, so client money has been tracked in the accounting package or a spreadsheet. Those records become the source for opening trust balances in the new system, and each one is agreed to the trust bank statement before it is loaded.

Does billing history from Harvest move into Google Drive?

No. Google Drive has no place for invoices or payments. Billing history from Harvest is exported as reports and invoice copies and kept as a readable archive.

What happens to records Google Drive has no place for?

On this route that is matters, contacts, tasks, time entries and billing records. They are exported from Harvest 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 Harvest data is loaded into Google Drive?

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

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

Moving from Harvest to Google Drive?

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

We reply within one business day.