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

Data migration route

TeamConnect data to Microsoft SQL Server

TeamConnect is a cloud case management system for in-house legal departments, and Microsoft SQL Server is a database on a server the firm runs. 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. Calendar: Exported in full
  4. Tasks: Exported in full
  5. Time and expenses: Exported in full
  6. Billing: Exported in full
  7. Intake: Exported in full
  8. Documents: Exported with mapping
  9. Emails: Exported with mapping
  10. Custom fields: Exported with mapping
  11. Templates: Exported with mapping
  12. Notes: Confirmed in the analysis
ToMicrosoft SQL ServerServer
  • 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 Microsoft SQL Server

Each row is a kind of record TeamConnect holds, whether Microsoft SQL Server 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 Microsoft SQL Server
RecordIn TeamConnectIn Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters with status, deadlines, budgets and assigned outside counsel.Has a placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeldPeople, companies and the law firms engaged on matters.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldDocuments are kept in context with each matter.Has a place in partAs files in folders with an index table; storing files in the database is possible.Exported with mapping
EmailsEmails saved to matters or to the storeHeld in partOutlook integration is listed; requests can also arrive by email.Has a place in partAs message files with an index table, or as rows of header fields.Exported with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeRows of text linked to matters and contacts.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldDeadlines and calendar events on matters.Has a placeRows of appointments and key dates; nothing displays them as a calendar.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldTasks, routing and escalations driven by workflow rules.Has a placeRows 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 placeTime and expense rows with rates 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 placeInvoices, lines and receipts as rows; invoice PDFs kept as files.Exported in full
Custom fieldsFields and record types the firm added itselfHeldMitratech describes the platform as highly configurable.Has a placeAs added columns, or a table of field names and values.Exported with mapping
TemplatesPrecedents, document templates and automationHeldReusable matter templates and configurable document templates.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLegal request intake and triage from the business.Has a placeEnquiry rows, where the source recorded them.Exported in full

What the plans mean

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

There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.

  1. Restored copy or rebuilt schema

    Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.

  2. No screens come with it

    A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.

  3. Documents sit beside the database

    Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.

  4. The edition follows the size

    A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.

  5. Backups and a test restore

    An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.

More about moving into Microsoft SQL Server

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 Microsoft SQL Server 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 Microsoft SQL Server 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 toMicrosoft SQL Server

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 Microsoft SQL Server. 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

Microsoft SQL Server 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.

Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.

What is agreed and set up

  • Server, instance and edition agreed with the IT provider
  • Read-only logins and roles for named staff
  • Views for matter, ledger, time and document look-ups
  • Backup schedule and who tests a restore
  • Plain names and descriptions for tables and columns
  • Excel or Power BI connected for reporting

Questions

TeamConnect to Microsoft SQL Server: 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 Microsoft SQL Server hold billing records from TeamConnect?

Yes. Invoices, lines and receipts as rows; invoice PDFs kept as files. 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 Microsoft SQL Server?

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 Microsoft SQL Server is kept as a readable archive, and you see which before the move.

What has to be decided before TeamConnect is written out to Microsoft SQL Server?

Documents, emails, custom fields and templates 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 Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.

Moving from TeamConnect to Microsoft SQL Server?

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

We reply within one business day.