Data migration route
Tabs3 to LexWorkplace migration
Tabs3 is a server-based practice management system, and LexWorkplace 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
- Notes: Carried across
- Matters: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Tasks: Confirmed in the analysis
LexWorkplaceCloud- Contacts: 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
- 3 carried
- 3 mapped
- 1 to confirm
- 7 archived
What moves
What moves from Tabs3 to LexWorkplace
Each row is a kind of record Tabs3 holds, whether LexWorkplace has a place for it, and what is planned. On this route three kinds of record carry across, three kinds need mapping, seven kinds have no place in LexWorkplace 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 partName, custom ID, client, type, location, staff, tags and dates. No parties or financial fields. | Carried with mapping |
| ContactsClients, other parties and referrers | Held | No placeOnly a client name, status, attorneys and tags. | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | Held in partPracticeMaster links documents to clients and contacts. | Has a placeFiled to a matter or to Firm Documents, in folders. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partPracticeMaster keeps email records in its Journal. | Has a placeOn the matter’s Email tab, in their own folders. | Carried across |
| NotesFile notes, matter notes and contact notes | Held in partNote, phone and research records in the PracticeMaster Journal. | Has a placeAs Matter Notes on the matter’s Notes tab. | Carried across |
| 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 place in partOld categories can become document types, statuses or tags. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partDocument assembly in PracticeMaster; statement layouts in Billing. | Has a place in partStored as files in Firm Documents. | 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
- LexWorkplace has a place for this kind of record. It is loaded there and checked against Tabs3.
- Carried with mapping
- LexWorkplace 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
- LexWorkplace 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. LexWorkplace 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 LexWorkplace 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. LexWorkplace 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 LexWorkplace
LexWorkplace expects every document and email to belong to a matter, so loading it starts with the matter list: name, custom ID, client, type and dates. Uptime Legal states that it runs migration and onboarding for its customers itself. The preparation is getting the old system’s content into a clean client and matter structure, with the exceptions resolved, ready for that load.
Matters carry little, by design
A matter record holds a name, a custom ID, a client, a type, a location, assigned staff, tags and open and close dates. Parties, court details and financial data have no fields. Those stay in the practice management system, and the two are tied together by using the same matter number as the custom ID.
Clients are only containers
LexWorkplace says plainly that its clients are for grouping matters, not for client management. A client has a name, a status, primary attorneys and tags. Addresses, phone numbers and contact history from the old system are not loaded here. They go to the practice management system or stay behind.
Three tabs per matter
Content arrives as documents, emails or notes, each on its own tab with its own folders. Emails held as message files in an old folder tree have to be recognised and loaded as emails, not as documents, or they will not appear where lawyers look for correspondence.
Closed matters and archive
A matter is closed by giving it a close date, and closed matters can be moved to archive storage, where they keep their place but are not searched or indexed until un-archived. Old matters can therefore be loaded and archived straight away. The firm sets the cut-off year.
Profiling is optional unless enforced
Document type, status and tags are not required by default, though a firm can switch on mandatory profiling for matters. If the old system had document types, they are mapped to LexWorkplace types during the load. If it had none, the firm chooses between loading unprofiled and assigning types by folder name.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in LexWorkplace on this route, which makes it repeatable: a load can be run again until it is right. The maker of LexWorkplace says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Tabs3 and checking each trial against Tabs3.
Analysis
We read what Tabs3 holds and how it is organised, then agree with you where each kind of record will sit in LexWorkplace. 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 LexWorkplace 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 LexWorkplace. 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 LexWorkplace
Loaded data is not yet a working system. The maker of LexWorkplace runs or arranges the set-up of its product, so this is what has to be decided and put in place in LexWorkplace, whoever does the work, before people rely on it from the first day.
Setting LexWorkplace up for a firm is a short list of decisions made in its settings, plus software on each computer. The decisions are what the firm calls its matter types, document types and statuses, who can open which matters by default, and whether versioning is automatic or manual. The Launcher and the Outlook add-in are then installed for every user.
Set-up decisions in LexWorkplace
- Matter types, document types, statuses and tag conventions
- Groups, rights and default permissions for new matters
- Automatic or manual versioning, and whether profiling is mandatory
- Linking matters to Clio Manage where the firm uses it
- Launcher, Office and Outlook add-ins on each Windows or Mac computer
- A Firm Documents structure for templates, policies and internal files
Questions
Tabs3 to LexWorkplace: 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 LexWorkplace?
No. LexWorkplace 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 LexWorkplace has no place for?
On this route that is contacts, 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 LexWorkplace?
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 LexWorkplace
Other destinations from Tabs3
Other systems that move into LexWorkplace
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 LexWorkplace are the names and marks of their owners, used here only to identify the two systems.
Moving from Tabs3 to LexWorkplace?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.