Data migration route
TXdocs to SharePoint migration
TXdocs is a cloud specialist tool, and SharePoint is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.
TXdocsCloud- Documents: Carried across
- Matters: Carried with mapping
- Contacts: Carried with mapping
- Emails: Carried with mapping
- Calendar: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
SharePointCloud- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 5 mapped
- 5 to confirm
- 3 archived
What moves
What moves from TXdocs to SharePoint
Each row is a kind of record TXdocs holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, five kinds need mapping, three kinds have no place in SharePoint and are archived and five kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCases, with the data entered for document assembly. | Has a place in partAs a site, library, folder or list row the firm designs; no built-in matter record. | Carried with mapping |
| ContactsClients, other parties and referrers | Held in partCase and contact management is part of TXdocsPlus. | Has a place in partOnly as rows in a list built for the purpose. | Carried with mapping |
| DocumentsFiles stored in or linked from the system | HeldDocuments assembled from the forms library. Storage detail is confirmed in the analysis. | Has a placeFiles in libraries, with columns and versions. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partEmail management is listed as a TXdocsPlus feature. | Has a place in partAs .msg or .eml files, with columns for sender and date if set up. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place in partAs documents, or as rows in a notes list if one is built. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partCalendaring and deadline tools are in TXdocsPlus. | Has a place in partPossible as a list; usually left in Outlook. | Carried with mapping |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a place in partPossible as a list; no legal workflow built in. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | Held in partTime slips, in TXdocsPlus. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | Held in partIndividual and periodic bills, in TXdocsPlus. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | No place | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmedFinancial reports are included. A general ledger is not confirmed. | No place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeColumns and content types on libraries and lists. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldAutomated Texas forms from TXdocs, plus the firm’s own customisations. | Has a place in partPrecedents as files; templates can be offered from a library. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldOnline intake questionnaires that clients complete. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- SharePoint has a place for this kind of record. It is loaded there and checked against TXdocs.
- Carried with mapping
- SharePoint 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
- SharePoint has no place for it. It is exported in a format that opens without TXdocs 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 TXdocs into SharePoint 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 SharePoint 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 TXdocs.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of TXdocs 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 TXdocs is kept running until the checks on SharePoint are finished.
Where the data is now
Leaving TXdocs
What a firm has in TXdocs is mainly case data and the documents assembled from it, and for TXdocsPlus subscribers also time, bills, contacts and a calendar. The forms library belongs to TXdocs and stays with the subscription. A move takes the firm’s own records and finished documents, and plans how drafting will be done afterwards, since drafting is the reason the firm bought the product.
The forms stay behind
The automated Texas forms are TXdocs’ content, supplied by subscription, and are not carried into another system. What moves is each completed document and the case data behind it. Firms decide before cutover whether to keep a TXdocs subscription for drafting beside the new system, or rebuild their most-used documents as templates in the destination.
Standard or Plus
A TXdocs Standard firm has cases, intake answers and documents. A TXdocsPlus firm also has time slips, bills, a calendar, contacts and conflict data in the same account. Which plan the firm is on sets the scope. Billing history in particular needs a decision: balances only, or every bill and payment.
Case data shaped for forms
Information is entered once and reused across documents, so a divorce case may hold inventories and financial statements as structured answers. A general practice system has fields for only some of that. The rest is preserved as a generated summary document on the matter, so the answers are not lost.
Data is held by TXdocs
The software runs in a browser, and each firm’s data sits in a separate database on TXdocs’ servers. There is no local database for the firm’s IT provider to copy. How the firm’s records and documents are exported is confirmed with TXdocs at the start of the analysis, before a timetable is set.
Filed versions and drafts
Documents filed with Texas courts through the integrated eFiling should be kept apart from their drafts. Whether filing details can be exported as data is confirmed in the analysis. Either way, the filed version of each document is identified, so that it is the one a lawyer finds first on the matter.
Where it is going
Arriving in SharePoint
SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.
Site, library or folder per matter
A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.
Columns are built before content
If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.
The 400 character path
SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.
Large libraries and the view threshold
A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.
Security by library, not by file
Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in SharePoint on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what TXdocs holds and how it is organised, then agree with you where each kind of record will sit in SharePoint. 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 SharePoint and checked against TXdocs: 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 TXdocs, a final pass over a weekend picks up what changed since the trial. TXdocs 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 TXdocs 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 TXdocs holds
What is in it, how its records link, and where each piece would sit in SharePoint. 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
SharePoint 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.
Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.
What is agreed and set up
- Site and library structure for clients and matters
- Columns and content types for matter number and document type
- Permission groups, with restricted matters in their own libraries
- A repeatable way to create each new matter’s workspace
- Version history limits and retention labels for closed matters
- Views, indexed columns and search tested on loaded data
Questions
TXdocs to SharePoint: what firms ask
Can our TXdocs forms be moved into the new system?
No. The forms library is TXdocs’ own content and is tied to the subscription. Your finished documents move, and so does your case data. Drafting afterwards is done either by keeping TXdocs for assembly, or by building templates in the new system for the documents you produce most. That choice is made early.
We use TXdocsPlus for billing. What happens to our time and bills?
Unbilled time, open bills and client balances are the minimum that moves, so billing can continue without a gap. Whether older bills and payments come across as history depends on what the destination accepts and what TXdocs can export. The totals are checked against TXdocs reports on the trial load.
Do trust balances in TXdocs have a place in SharePoint?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in TXdocs before the plan is fixed. If SharePoint turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
What happens to records SharePoint has no place for?
On this route that is time entries, billing records and intake records. They are exported from TXdocs 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 TXdocs data is loaded into SharePoint?
Matters, contacts, emails, calendar entries and templates are carried with mapping, so each mapping is agreed with you first. Notes, tasks, trust ledgers, the firm’s accounts and custom fields 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 TXdocs and into SharePoint
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.
TXdocs and SharePoint are the names and marks of their owners, used here only to identify the two systems.
Moving from TXdocs to SharePoint?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.