Data migration route
TeamConnect to LexWorkplace migration
TeamConnect is a cloud case management system for in-house legal departments, 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.
TeamConnectCloud- Documents: Carried across
- Emails: Carried across
- Matters: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- 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
- Intake: Kept as a readable archive
- 2 carried
- 3 mapped
- 2 to confirm
- 5 archived
What moves
What moves from TeamConnect to LexWorkplace
Each row is a kind of record TeamConnect holds, whether LexWorkplace has a place for it, and what is planned. On this route two kinds of record carry across, three kinds need mapping, five kinds have no place in LexWorkplace and are archived and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldMatters with status, deadlines, budgets and assigned outside counsel. | 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 | HeldPeople, companies and the law firms engaged on matters. | No placeOnly a client name, status, attorneys and tags. | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldDocuments are kept in context with each matter. | Has a placeFiled to a matter or to Firm Documents, in folders. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partOutlook integration is listed; requests can also arrive by email. | Has a placeOn the matter’s Email tab, in their own folders. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeAs Matter Notes on the matter’s Notes tab. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldDeadlines and calendar events on matters. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | HeldTasks, routing and escalations driven by workflow rules. | To be confirmed | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | Held in partTime can be captured on matters by the in-house team. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | Held in partInvoices received from outside counsel through e-billing, not bills issued to clients. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldMitratech describes the platform as highly configurable. | Has a place in partOld categories can become document types, statuses or tags. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldReusable matter templates and configurable document templates. | Has a place in partStored as files in Firm Documents. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLegal request intake and triage from the business. | 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 TeamConnect.
- 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 TeamConnect 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 TeamConnect 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 TeamConnect for matters and billing, or into an archive.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of TeamConnect 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 TeamConnect is kept running until the checks on LexWorkplace are finished.
Where the data is now
Leaving TeamConnect
TeamConnect data is a legal department’s view of its matters: what the matter is, which firm is acting, what has been budgeted and what has been invoiced and approved. Moving it into a law firm practice system, or into another department tool, means translating that view. Invoices here are bills received, not bills issued, and that difference runs through the whole mapping.
Bills received, not issued
E-billing in TeamConnect holds invoices submitted by outside law firms, with line items, adjustments and approvals. A law firm practice system treats invoices as money owed to the firm. Spend history is mapped to wherever the destination records costs on a matter, or kept as a report, never loaded as receivables.
Every installation is configured
Mitratech sells the platform as highly configurable, and departments add their own fields, categories and workflow rules. No two data models are quite alike. The analysis starts from the organisation’s own configuration and lists each custom field with the place it will take in the new system.
Cloud or on-premises
The product runs either in Mitratech’s cloud or on servers the organisation controls. On-premises, the database can be copied for analysis. In the cloud, the data comes through whatever exports and interfaces the service provides. Which one applies is confirmed first, as it sets how the extraction is done.
Outside counsel as records
Law firms, their timekeepers and agreed rates are part of the data, linked to the matters they work on. In a practice system the nearest equivalent is a contact with a role on the matter. Rate agreements and firm performance data usually have no field and are carried as notes or left in an archive.
Intake requests from the business
Requests for legal help arrive through intake forms, email, Slack or Teams and are routed to a lawyer. Open requests that have not yet become matters are easy to miss. They are counted separately and either converted to matters before cutover or brought across as enquiries.
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 TeamConnect and checking each trial against TeamConnect.
Analysis
We read what TeamConnect 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 TeamConnect: 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 TeamConnect, a final pass over a weekend picks up what changed since the trial. TeamConnect 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 TeamConnect 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 TeamConnect 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
TeamConnect to LexWorkplace: what firms ask
We are a legal department, not a law firm. Does a practice management system fit?
Sometimes. Practice systems are built around billing clients, which a department does not do. They work where the need is matter files, documents and deadlines. If tracking outside counsel spend and approving invoices is central, the destination has to support that, and the analysis says plainly where it does not.
What happens to approved invoice history?
Each invoice from outside counsel is read with its matter, firm, amounts billed, adjustments and approval status. If the new system has a place for costs against a matter, totals are loaded there. Line-level detail is usually exported to a reporting file and kept with the read only copy of the old system.
Do documents come across with their matters?
Documents stored against a matter are extracted with the matter reference, file name and dates, then loaded into the matching matter in the destination. Counts per matter are compared before and after. Where the organisation also files to a separate document system from TeamConnect, that store is handled on its own.
Does billing history from TeamConnect move into LexWorkplace?
No. LexWorkplace has no place for invoices or payments. Billing history from TeamConnect is exported as reports and invoice copies and kept as a readable archive.
What happens to records LexWorkplace has no place for?
On this route that is contacts, calendar entries, time entries, billing records and intake records. They are exported from TeamConnect 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 TeamConnect data is loaded into LexWorkplace?
Matters, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes and 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 TeamConnect and 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.
TeamConnect and LexWorkplace are the names and marks of their owners, used here only to identify the two systems.
Moving from TeamConnect 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.