Data migration route
TeamConnect to Sync.com migration
TeamConnect is a cloud case management system for in-house legal departments, and Sync.com is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.
TeamConnectCloud- Documents: Carried across
- Emails: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
Sync.comCloud- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Tasks: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Custom fields: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 2 mapped
- 1 to confirm
- 8 archived
What moves
What moves from TeamConnect to Sync.com
Each row is a kind of record TeamConnect holds, whether Sync.com has a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping, eight kinds have no place in Sync.com and are archived 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. | No placeA matter is a folder in Files or Vault. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldPeople, companies and the law firms engaged on matters. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldDocuments are kept in context with each matter. | Has a placeFiles and folders within the path limit; some file types are skipped by the apps. | 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 partMessage files such as .msg or .eml, filed in the matter’s folder. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place in partOnly as a document written out to the matter’s folder. | 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. | No place | Kept as a readable archive |
| 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. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | HeldReusable matter templates and configurable document templates. | Has a place in partPrecedents load as ordinary files. | 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
- Sync.com has a place for this kind of record. It is loaded there and checked against TeamConnect.
- Carried with mapping
- Sync.com 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
- Sync.com 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 Sync.com 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 Sync.com 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 Sync.com 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 Sync.com
A firm that moves its files to Sync is usually doing so for confidentiality, and the load has to respect how the service is built to deliver it. Files are encrypted before they leave the computer. Nobody at Sync can look inside the account to confirm what arrived, so the checking is done from the firm’s side, against the list of what was sent.
Files or Vault
Open matters belong in Files, where they sync to the people working on them. Closed matters can go to Vault, which holds them in the cloud without putting a copy on every laptop. The firm supplies its open and closed matter lists so each folder is sent to the right side.
A 248 character path limit
Sync sets a maximum path length of 248 characters to stay compatible between Windows and Mac, and its apps skip anything longer. That is tighter than most systems a firm will be coming from. Folder names are shortened in the plan, and Sync’s own guidance favours a tree only a few levels deep.
What the apps leave out
The desktop apps do not upload shortcut files, temporary Office files or names containing a slash, and they warn against several other characters on Windows. A copy to Vault produces a transfer report listing what was skipped. That report is reconciled against the source file list after every load.
Permissions come from the top folder
Sharing is set on a folder and flows down to all of its contents. A matter that needs different access from the rest of a client’s work cannot simply sit one level down with tighter settings. It becomes its own shared folder, and those exceptions are identified before the tree is built.
Shared folders count against storage
A shared folder is added to each member’s account and normally counts towards their quota, and it syncs to their computer as a real folder. Sharing the whole client tree with every person can fill both. Shares are sized to teams, and the allowance needed per user is worked out from the document volumes.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Sync.com on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what TeamConnect holds and how it is organised, then agree with you where each kind of record will sit in Sync.com. 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 Sync.com 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 Sync.com. 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
Structure, permissions and handover
Sync.com 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.
A Sync set-up comes down to accounts and shares. A team plan gives an administrator control over users, two-factor authentication and password resets, which matters more than usual in a service the provider says it cannot see into. The shared folders are then created to match the firm’s teams and its restricted matters.
What is agreed and set up
- Administrator account and a user for each staff member
- Two-factor authentication enforced across the firm
- Team shared folders with view or edit permission per person
- Which matters live in Files and which in Vault
- Rules for client links: passwords, expiry dates, upload rights
- Desktop app installed, with a filing guide for new matters
Questions
TeamConnect to Sync.com: 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 Sync.com?
No. Sync.com 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 Sync.com has no place for?
On this route that is matters, contacts, calendar entries, tasks, time entries, billing records, custom fields 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 Sync.com?
Emails 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.
Other routes
Other routes from TeamConnect and into Sync.com
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 Sync.com are the names and marks of their owners, used here only to identify the two systems.
Moving from TeamConnect to Sync.com?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.