Data migration route
Harvest to NetDocuments migration
Harvest is a cloud accounting and billing system, and NetDocuments is a cloud document management system. Only files and their details have a place there, so this route carries the documents and archives the rest.
HarvestCloud- Matters: Carried with mapping
- Documents: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
NetDocumentsCloud- Contacts: Kept as a readable archive
- Notes: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- 1 mapped
- 4 to confirm
- 4 archived
What moves
What moves from Harvest to NetDocuments
Each row is a kind of record Harvest holds, whether NetDocuments has a place for it, and what is planned. On this route one kind needs mapping, four kinds have no place in NetDocuments and are archived and four 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 client and matter value with its workspace. Other matter details stay in practice management. | Carried with mapping |
| ContactsClients, other parties and referrers | Held in partClients and client contacts, kept mainly as invoice recipients. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | To be confirmed | Has a placeImported with profile values, folder, dates and access set per document. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held in partFree-text notes on each time entry. | No placeFile notes are loaded as documents in the matter workspace. | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | Held in partTasks are categories of work for time entries, not to-dos. | To be confirmed | Confirmed in the analysis |
| 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 placeAs custom profile attributes, created in the repository before the load. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh. | Confirmed in the analysis |
What the plans mean
- Carried with mapping
- NetDocuments 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
- NetDocuments 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
Only the documents have a place here.
NetDocuments is a document management system: it takes files and the details that describe them. Most of what Harvest holds is not files. Entries, balances, settings and lists have no place in a document store, and the table above is short for that reason. What can move is any document Harvest produced or stored: invoices as PDFs, signed agreements, attachments, exported reports. Each is filed under the client or matter it relates to.
The useful version of this job is often an archive. A firm retiring a system wants its records readable later without keeping the subscription or the old PC. The data is exported in open formats, spreadsheets and PDFs, and filed in NetDocuments in a workspace set aside for it, with access limited to the people who need it. That gives the firm one place to look, under the same retention rules as the rest of its documents.
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 NetDocuments 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 NetDocuments
Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.
Lookup tables before documents
Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.
Workspaces come from the profile
A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.
Import files are unforgiving
The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.
Folder limits and depth
A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.
Security at the right level
Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in NetDocuments 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 NetDocuments. 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 NetDocuments 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 NetDocuments. 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
Setting up NetDocuments
Loaded data is not yet a working system. This is what NewLaw sets up in NetDocuments, beyond the migration, so that people can work in it from the first day.
Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.
Set-up decisions in NetDocuments
- Cabinet design: one for the firm, or several by purpose
- Profile attributes, lookup tables and the client and matter hierarchy
- Workspace layout with default folders, filters and saved searches
- User groups, cabinet membership and security for restricted matters
- A feed of new clients and matters from practice management
- ndOffice, ndMail and Outlook filing on every desk, with training
Questions
Harvest to NetDocuments: 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 NetDocuments?
No. NetDocuments 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 NetDocuments has no place for?
On this route that is contacts, notes, 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 NetDocuments?
Matters are carried with mapping, so each mapping is agreed with you first. Documents, tasks, 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 NetDocuments
Other destinations from Harvest
Other systems that move into NetDocuments
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 NetDocuments are the names and marks of their owners, used here only to identify the two systems.
Moving from Harvest to NetDocuments?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.