Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

TeamConnect data to Full data export

TeamConnect is a cloud case management system for in-house legal departments, and Full data export is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what TeamConnect holds and keeps it readable and open to queries.

FromTeamConnectCloud
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Documents: Exported in full
  4. Calendar: Exported in full
  5. Tasks: Exported in full
  6. Time and expenses: Exported in full
  7. Billing: Exported in full
  8. Emails: Exported with mapping
  9. Custom fields: Exported with mapping
  10. Templates: Exported with mapping
  11. Intake: Exported with mapping
  12. Notes: Confirmed in the analysis
ToFull data exportFiles
  • 7 carried
  • 4 mapped
  • 1 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from TeamConnect to Full data export

Each row is a kind of record TeamConnect holds, whether Full data export has a place for it, and what is planned. On this route seven kinds of record carry across, four kinds need mapping and one kind is confirmed in the analysis.

Records in TeamConnect and their place in Full data export
RecordIn TeamConnectIn Full data exportWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters with status, deadlines, budgets and assigned outside counsel.Has a placeA matters table keyed by the original matter number.Exported in full
ContactsClients, other parties and referrersHeldPeople, companies and the law firms engaged on matters.Has a placeA contacts table and a table of each contact’s role on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldDocuments are kept in context with each matter.Has a placeFiles under their original names, in client and matter folders.Exported in full
EmailsEmails saved to matters or to the storeHeld in partOutlook integration is listed; requests can also arrive by email.Has a place in partFiled emails as message files in the matter’s folder, if the source exposes them.Exported with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeA notes table with matter, author and date for each note.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldDeadlines and calendar events on matters.Has a placeA table of appointments and key dates; nothing shows it as a diary.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldTasks, routing and escalations driven by workflow rules.Has a placeA table of tasks with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeld in partTime can be captured on matters by the in-house team.Has a placeA time entries table with fee earner, matter, units, rate and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeld in partInvoices received from outside counsel through e-billing, not bills issued to clients.Has a placeInvoice, line and receipt tables; invoice PDFs can be kept beside them.Exported in full
Custom fieldsFields and record types the firm added itselfHeldMitratech describes the platform as highly configurable.Has a placeExtra columns under their original field names.Exported with mapping
TemplatesPrecedents, document templates and automationHeldReusable matter templates and configurable document templates.Has a place in partTemplate files only; the merge fields in them will not run.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLegal request intake and triage from the business.Has a place in partAn enquiries table, where the source tracked leads.Exported with mapping

What the plans mean

Exported in full
Full data export has a place for this kind of record. It is loaded there and checked against TeamConnect.
Exported with mapping
Full data export 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

Not a new system. A complete copy the firm can query.

Writing TeamConnect out to Full data export is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in TeamConnect as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

TeamConnect is hosted by its maker and Full data export sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What TeamConnect will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving off TeamConnect

Where it is going

A full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.

  1. Tables that still join up

    Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.

  2. Documents with an index

    Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.

  3. Reports a person can read

    Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.

  4. What an export does not keep

    Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.

  5. Checked while the source is open

    Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.

More about moving into Full data export

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what TeamConnect holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything TeamConnect holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to Full data export as a trial and checked against TeamConnect: record counts, totals where TeamConnect holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in TeamConnect, the export is run a final time and checked again. There is nothing to go live. TeamConnect is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

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

Step 1 of 5: Start with the route

Moving fromTeamConnect
Moving toFull data export

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what TeamConnect holds

    What is in it, how its records link, and where each piece would sit in Full data export. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. 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

Structure, permissions and handover

Full data export is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.

What is agreed and set up

  • Folder layout for tables, documents and reports
  • What the key to tables, columns and identifiers records
  • Where the copies are stored and who is custodian
  • Who may open it, as approved by a partner
  • Which look-ups staff must be able to do unaided
  • Retention period and the date it is next reviewed

Questions

TeamConnect to Full data export: 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 the copy in Full data export hold billing records from TeamConnect?

Yes. Invoice, line and receipt tables; invoice PDFs can be kept beside them. Billing records are written out with the rest, and counts and totals are agreed to the reports in TeamConnect as at the export date.

Does everything in TeamConnect have a place in Full data export?

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 Full data export is kept as a readable archive, and you see which before the move.

What has to be decided before TeamConnect is written out to Full data export?

Emails, custom fields, templates and intake records are exported with mapping, so each mapping is agreed with you first. Notes are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.

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.

How we do itDiscovery to rollout, step by step

TeamConnect and Full data export are the names and marks of their owners, used here only to identify the two systems.

Moving from TeamConnect to Full data export?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.