Data migration route
TeamConnect to Neos migration
TeamConnect is a cloud case management system for in-house legal departments. Neos is a case management system for personal injury work, run the same way. The records line up case for case, and the detail is in the fields and stages.
TeamConnectCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Intake: Carried across
- Emails: Carried with mapping
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
NeosCloud- 6 carried
- 5 mapped
- 1 to confirm
What moves
What moves from TeamConnect to Neos
Each row is a kind of record TeamConnect holds, whether Neos has a place for it, and what is planned. On this route six kinds of record carry across, five kinds need mapping and one kind is 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 placeCases by case type. | Carried across |
| ContactsClients, other parties and referrers | HeldPeople, companies and the law firms engaged on matters. | Has a placeParties, providers and case contacts. Contacts can be imported from CSV. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldDocuments are kept in context with each matter. | Has a placeCase Docs tab, organised in sub-tabs. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partOutlook integration is listed; requests can also arrive by email. | Has a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldDeadlines and calendar events on matters. | Has a placeCase calendar entries. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTasks, routing and escalations driven by workflow rules. | Has a placeLoaded as checklist items. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | Held in partTime can be captured on matters by the in-house team. | Has a place in partTime can be held as value items. The treatment of old entries is confirmed in the analysis. | Carried with mapping |
| BillingInvoices, payments and debtor balances | Held in partInvoices received from outside counsel through e-billing, not bills issued to clients. | Has a place in partInvoices exist in Neos. Loading past invoices is confirmed in the analysis. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | HeldMitratech describes the platform as highly configurable. | Has a placeUser-defined fields are created on the relevant tab first. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldReusable matter templates and configurable document templates. | Has a place in partTemplates are rebuilt for Neos document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLegal request intake and triage from the business. | Has a placeIntakes tab. Simple intake imports from CSV are supported. | Carried across |
What the plans mean
- Carried across
- Neos has a place for this kind of record. It is loaded there and checked against TeamConnect.
- Carried with mapping
- Neos 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.
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
Case to case, field by field.
Two case management systems look alike from a distance and differ in almost every detail. Each has its own idea of a case type, a stage, a party role and a deadline. TeamConnect and Neos may both hold a limitation date, yet one calculates it and the other stores what was typed. The mapping goes field by field and status by status, and the trial load is checked by opening real cases in both systems side by side.
Custom fields hold most of what the firm has built up. Years of intake answers, injury details or visa histories sit in fields the firm added itself. Each is matched to a field in Neos, and anything unmatched is kept as a note on the case so that it can still be searched. Workflows and document templates are rebuilt in the new system’s own tools. Open tasks come across with their owners and due dates.
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 Neos 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 Neos
Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.
Every figure needs a value code
Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.
Lists are set up first
Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.
Documents go to sub-tabs
Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.
Reminders split two ways
Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.
Assembly runs its own conversions
Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Neos 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 its records link, then agree with you, field by field, where each piece will sit in Neos. Anything with no place there comes across as a note or stays behind, and you see which before the move.
Clean-up
Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in TeamConnect, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Neos as a trial and checked against TeamConnect: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in TeamConnect are frozen for an agreed window, the data is collected a final time and Neos goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in TeamConnect as at the cutover date. 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 Neos. 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 Neos
Loaded data is not yet a working system. The maker of Neos runs or arranges the set-up of its product, so this is what has to be decided and put in place in Neos, whoever does the work, before people rely on it from the first day.
Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.
Set-up decisions in Neos
- Set case types, statuses and staff roles
- Agree the value code list with accounts staff
- Build checklists for each case type and stage
- Create user-defined fields for data the tabs lack
- Prepare document templates for the generation wizard
- Connect Microsoft 365, QuickBooks and the phone system
Questions
TeamConnect to Neos: 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 Neos?
In part. Invoices exist in Neos. Loading past invoices is confirmed in the analysis. Open items are matched to what Neos can hold, and the rest of the billing history is kept as reports that open without TeamConnect.
Does everything in TeamConnect have a place in Neos?
Most of it does on paper. Notes could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Neos is kept as a readable archive, and you see which before the move.
What has to be decided before TeamConnect data is loaded into Neos?
Emails, time entries, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from TeamConnect and into Neos
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 Neos are the names and marks of their owners, used here only to identify the two systems.
Moving from TeamConnect to Neos?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.