Data migration route
Harvest to SharePoint migration
Harvest is a cloud accounting and billing system, and SharePoint is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.
HarvestCloud- Matters: Carried with mapping
- Contacts: Carried with mapping
- Notes: Carried with mapping
- Tasks: Carried with mapping
- Documents: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
SharePointCloud- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- 4 mapped
- 3 to confirm
- 2 archived
What moves
What moves from Harvest to SharePoint
Each row is a kind of record Harvest holds, whether SharePoint has a place for it, and what is planned. On this route four kinds need mapping, two kinds have no place in SharePoint and are archived and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partProjects under clients stand in for matters; there are three project types. | Has a place in partAs a site, library, folder or list row the firm designs; no built-in matter record. | Carried with mapping |
| ContactsClients, other parties and referrers | Held in partClients and client contacts, kept mainly as invoice recipients. | Has a place in partOnly as rows in a list built for the purpose. | Carried with mapping |
| DocumentsFiles stored in or linked from the system | To be confirmed | Has a placeFiles in libraries, with columns and versions. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held in partFree-text notes on each time entry. | Has a place in partAs documents, or as rows in a notes list if one is built. | Carried with mapping |
| TasksTo-dos and workflow steps assigned to people | Held in partTasks are categories of work for time entries, not to-dos. | Has a place in partPossible as a list; no legal workflow built in. | Carried with mapping |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimers and timesheets by person, project and task, with approvals. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldInvoices and estimates, with online payment through Stripe or PayPal. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeColumns and content types on libraries and lists. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partPrecedents as files; templates can be offered from a library. | Confirmed in the analysis |
What the plans mean
- Carried with mapping
- SharePoint 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
- SharePoint 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.
SharePoint 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 SharePoint 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 SharePoint are finished.
Where the data is now
Leaving Harvest
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in SharePoint
SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.
Site, library or folder per matter
A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.
Columns are built before content
If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.
The 400 character path
SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.
Large libraries and the view threshold
A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.
Security by library, not by file
Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in SharePoint on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Harvest holds and how it is organised, then agree with you where each kind of record will sit in SharePoint. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into SharePoint 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.
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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Harvest holds
What is in it, how its records link, and where each piece would sit in SharePoint. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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
SharePoint 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.
Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.
What is agreed and set up
- Site and library structure for clients and matters
- Columns and content types for matter number and document type
- Permission groups, with restricted matters in their own libraries
- A repeatable way to create each new matter’s workspace
- Version history limits and retention labels for closed matters
- Views, indexed columns and search tested on loaded data
Questions
Harvest to SharePoint: 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 SharePoint?
No. SharePoint 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 SharePoint has no place for?
On this route that is 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 SharePoint?
Matters, contacts, notes and tasks 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.
Other routes
Other routes from Harvest and into SharePoint
Other destinations from Harvest
Other systems that move into SharePoint
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Harvest and SharePoint are the names and marks of their owners, used here only to identify the two systems.
Moving from Harvest to SharePoint?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.