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

Data migration route

TeamConnect to Box migration

TeamConnect is a cloud case management system for in-house legal departments, and Box is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

FromTeamConnectCloud
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Custom fields: Carried with mapping
  4. Templates: Carried with mapping
  5. Notes: Confirmed in the analysis
ToBoxCloud
  1. Matters: Kept as a readable archive
  2. Contacts: Kept as a readable archive
  3. Calendar: Kept as a readable archive
  4. Tasks: Kept as a readable archive
  5. Time and expenses: Kept as a readable archive
  6. Billing: Kept as a readable archive
  7. Intake: Kept as a readable archive
Readable archiveNo place in Box
  • 1 carried
  • 3 mapped
  • 1 to confirm
  • 7 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from TeamConnect to Box

Each row is a kind of record TeamConnect holds, whether Box has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping, seven kinds have no place in Box and are archived and one kind is confirmed in the analysis.

Records in TeamConnect and their place in Box
RecordIn TeamConnectIn BoxWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters with status, deadlines, budgets and assigned outside counsel.No placeA matter is a folder, optionally with metadata; there is no matter record.Kept as a readable archive
ContactsClients, other parties and referrersHeldPeople, companies and the law firms engaged on matters.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldDocuments are kept in context with each matter.Has a placeFiles and folders, named and dated as they are loaded.Carried across
EmailsEmails saved to matters or to the storeHeld in partOutlook integration is listed; requests can also arrive by email.Has a place in partAs .msg or .eml files in the matter folder.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs documents in the matter folder, not as a notes record.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldDeadlines and calendar events on matters.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTasks, routing and escalations driven by workflow rules.No placeKept as a readable archive
Time and expensesTime and expense entries, billed and unbilledHeld in partTime can be captured on matters by the in-house team.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeld in partInvoices received from outside counsel through e-billing, not bills issued to clients.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldMitratech describes the platform as highly configurable.Has a place in partMetadata templates can hold fields such as matter number and client.Carried with mapping
TemplatesPrecedents, document templates and automationHeldReusable matter templates and configurable document templates.Has a place in partPrecedents load as ordinary files; no document automation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLegal request intake and triage from the business.No placeKept as a readable archive

What the plans mean

Carried across
Box has a place for this kind of record. It is loaded there and checked against TeamConnect.
Carried with mapping
Box 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
Box 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

Out of the system, into folders the firm can read.

File storage has folders and files and nothing else. Moving from TeamConnect into Box means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Box does not allow in a name.

Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in TeamConnect.

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 Box are finished.

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

Loading a firm’s files into Box means deciding the folder tree and its owners first, because permissions follow the tree. Box has no matter record. A matter is a folder, and anything else the firm knew about it, such as the matter number, client or status, survives only in the folder name or in metadata fields set up before the load.

  1. Decide who owns the top level

    Box’s own planning guidance sets out two models: users create their own top-level folders, or administrators own them all and invite people in. For matter files most later decisions depend on this one, including who can share outside the firm and whose storage allowance the files count against.

  2. Restricted matters go near the top

    Access in Box only flows downward. A person who can open a client folder can open every matter under it, and a subfolder cannot be hidden from them. Matters behind an information barrier therefore need their own top-level folders, and the list of those matters is agreed before the structure is built.

  3. Names Box will not accept

    Box rejects a slash or backslash anywhere in a file or folder name, and spaces at the start or end. Files from older systems and from Macs often have both. They are renamed by rule before loading and the firm receives the list, so that a document cited by its old name can still be found.

  4. Matter details become metadata

    A metadata template can hold the matter number, client name, practice area and closed date against each matter folder. The template has to exist before the files arrive so the values can be written during the load. Without it, the folder name is the only place that information lives.

  5. File size follows the owner’s plan

    The largest file Box accepts depends on the plan of whoever owns the folder. Litigation matters with video or forensic images are where this bites. Oversized files are found in the analysis, and the firm chooses between a higher plan and keeping those files somewhere else.

More about moving into Box

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Box on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what TeamConnect holds and how it is organised, then agree with you where each kind of record will sit in Box. Anything with no place there stays behind or is archived, and you see which before the move.

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

  3. Trial load

    A trial is loaded into Box 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.

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

Step 1 of 5: Start with the route

Moving fromTeamConnect
Moving toBox

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

Box is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

Most of a Box set-up is governance. The folder tree, the groups that are invited into it and the rules on sharing outside the firm are decided and built before any file is loaded. After the load, staff need Box Drive on their PCs and a short written guide to where a new matter folder is created and who creates it.

What is agreed and set up

  • Top-level folder structure and who owns each folder
  • Groups for teams, mapped to collaborator roles
  • Metadata template for matter number, client and status
  • Shared link defaults and rules for external collaborators
  • Box Drive installed and signed in on each PC
  • Version limits and retention agreed with the firm’s records policy

Questions

TeamConnect to Box: 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 Box?

No. Box 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 Box has no place for?

On this route that is matters, contacts, calendar entries, tasks, 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 Box?

Emails, 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 decides which closed matters and how many versions of a document are in scope.

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 Box are the names and marks of their owners, used here only to identify the two systems.

Moving from TeamConnect to Box?

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

We reply within one business day.