Data migration route
Tabs3 to NetDocuments migration
Tabs3 is a server-based practice management system, and NetDocuments is a cloud document management system. Documents and email move, filed under the matters they came from. Time, billing and trust have no place in a document system.
Tabs3Server- Documents: Carried across
- Emails: Carried across
- Matters: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Tasks: Confirmed in the analysis
NetDocumentsCloud- Contacts: Kept as a readable archive
- Notes: Kept as a readable archive
- Calendar: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Trust money: Kept as a readable archive
- Firm accounts: Kept as a readable archive
- Intake: Kept as a readable archive
- 2 carried
- 3 mapped
- 1 to confirm
- 8 archived
What moves
What moves from Tabs3 to NetDocuments
Each row is a kind of record Tabs3 holds, whether NetDocuments has a place for it, and what is planned. On this route two kinds of record carry across, three kinds need mapping, eight kinds have no place in NetDocuments and are archived and one kind is confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldA matter is the part of the Client ID after the decimal point. | 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 | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | Held in partPracticeMaster links documents to clients and contacts. | Has a placeImported with profile values, folder, dates and access set per document. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partPracticeMaster keeps email records in its Journal. | Has a placeLoaded as email items profiled to the matter. | Carried across |
| NotesFile notes, matter notes and contact notes | Held in partNote, phone and research records in the PracticeMaster Journal. | No placeFile notes are loaded as documents in the matter workspace. | Kept as a readable archive |
| CalendarAppointments, court dates and deadlines | Held in partIn PracticeMaster. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | Held in partIn PracticeMaster. | To be confirmed | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldIn Tabs3 Billing, with timers in PracticeMaster. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldIn Tabs3 Billing. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | Held in partWith the Trust Accounting module. | No place | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | Held in partWith the General Ledger and Accounts Payable modules. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | Held in partPracticeMaster Areas of Practice carry the firm’s own files and fields. | Has a placeAs custom profile attributes, created in the repository before the load. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partDocument assembly in PracticeMaster; statement layouts in Billing. | Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partTabs3 CRM covers leads and intake and works with PracticeMaster. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- NetDocuments has a place for this kind of record. It is loaded there and checked against Tabs3.
- 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 Tabs3 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 documents move. The accounts do not.
Moving from a matter system into a document management system is a documents job. NetDocuments has no place for time, invoices or trust, so there is no financial cutover on this route. What it does want is structure. Every document from Tabs3 is filed into a workspace or folder for its client and matter, with a profile that says what it is. The client and matter list becomes that structure, which is why it is cleaned before any file is copied.
A document’s own details count for more here than anywhere. Created and modified dates, author, document type and version become searchable profile fields, and a wrong date on a few thousand files is hard to undo. Email filed to matters is carried as messages. Document copies can be run again, so the trial is repeated until counts and dates agree. Matter data that NetDocuments cannot hold goes to whatever replaces Tabs3 for matters and billing, or into an archive.
Tabs3 runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. NetDocuments is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving Tabs3
The first question for a firm on Tabs3 is which modules it owns, because each one is a different set of records. Billing holds time, fees and receivables. PracticeMaster holds contacts, calendar, documents and the journal. Trust, payables and the ledger are separate programs again. All of them share the Client ID, which is what ties a move together.
One ID for client and matter
A Client ID is up to twelve characters including a decimal point. The part before the point is the client and the part after is the matter. Firms chose a numeric, alphabetic or mixed key type at set-up, and how many decimal places to allow. The ID is split on the way out and both halves are kept.
Everything in one directory
The modules integrate only when installed in the same directory, which the software calls the current working directory. Its data is a set of DAT and IDX files there. A complete copy of that directory, taken with all users out, is the source for every trial load.
Standard and Platinum
The Platinum edition adds a server component with scheduled HotBackup and SQL access to the data, and the standard edition has neither. Which edition the firm runs changes how a consistent copy is taken and what can read it, so it is established in the first conversation.
Figures that are not stored
The vendor’s own help notes that accounts receivable and work in process are calculated from ledger and fee records, not held as fields. So balances cannot be lifted out as a column. They are rebuilt from the transactions and then agreed to the reports the firm prints.
Cloud or server
Firms on Tabs3 Cloud use the suite as hosted by the vendor, and some on-premises firms run it with one of the vendor’s hosting partners. Where the files are, and who is able to copy them, is settled before a cutover date is set.
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 Tabs3 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 Tabs3: 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 Tabs3, a final pass over a weekend picks up what changed since the trial. Tabs3 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 Tabs3 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 Tabs3 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
Tabs3 to NetDocuments: what firms ask
We only have Tabs3 Billing and PracticeMaster. Is that a problem?
No. It means trust and the general ledger are kept in some other program, and that program is added to the plan. The move covers what Tabs3 holds, and the analysis names the other systems that have to agree with it at cutover.
Can we keep the client dot matter numbering?
If the destination allows a firm-set matter number, the full ID can be kept as it is, decimal point included. Where clients and matters are numbered separately, the two halves go into their own fields. Either way the original ID stays searchable, because it is printed on years of statements.
How are the modules extracted together?
From one copy of the working directory, taken at one moment, so billing, trust and ledger all describe the same day. Taking them at different times is how totals end up disagreeing. For the final cutover the copy is taken after month-end procedures are run and before anyone posts again.
Do trust balances in Tabs3 have a place in NetDocuments?
No. NetDocuments does not keep trust ledgers. Trust records from Tabs3 are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.
What happens to records NetDocuments has no place for?
On this route that is contacts, notes, calendar entries, time entries, billing records, trust ledgers, the firm’s accounts and intake records. They are exported from Tabs3 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 Tabs3 data is loaded into NetDocuments?
Matters, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Tasks 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 Tabs3 and into NetDocuments
Other destinations from Tabs3
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.
Tabs3 and NetDocuments are the names and marks of their owners, used here only to identify the two systems.
Moving from Tabs3 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.