Data migration route
CosmoLex data to Microsoft SQL Server
CosmoLex is a cloud practice management system, 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 CosmoLex holds and keeps it readable and open to queries.
CosmoLexCloud- Matters: Exported in full
- Contacts: Exported in full
- Notes: Exported in full
- Calendar: Exported in full
- Tasks: Exported in full
- Time and expenses: Exported in full
- Billing: Exported in full
- Trust money: Exported in full
- Firm accounts: Exported in full
- Intake: Exported in full
- Documents: Exported with mapping
- Emails: Exported with mapping
- Custom fields: Exported with mapping
- Templates: Exported with mapping
Microsoft SQL ServerServer- 10 carried
- 4 mapped
What moves
What moves from CosmoLex to Microsoft SQL Server
Each row is a kind of record CosmoLex holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route ten kinds of record carry across and four kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldEach has a Matter File #, an area of law and a matter owner. | Has a placeA table of matters linked to clients, parties and fee earners. | Exported in full |
| ContactsClients, other parties and referrers | HeldClients and other contacts; payees for accounts payable are a separate list. | Has a placePeople and companies, with their roles on each matter. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldBuilt-in storage, or OneDrive, Google Drive, Dropbox, Box or NetDocuments linked by 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 store | Held in partEmails sent to the firm’s forwarding address are tagged to matters by sender or recipient. | 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 notes | Held | Has a placeRows of text linked to matters and contacts. | Exported in full |
| CalendarAppointments, court dates and deadlines | Held | Has a placeRows of appointments and key dates; nothing displays them as a calendar. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | HeldTask workflows can be loaded into new or existing matters. | Has a placeRows with assignee, due date and status. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | HeldEntries are called timecards. | Has a placeTime and expense rows with rates and billed status. | Exported in full |
| BillingInvoices, payments and debtor balances | Held | Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | HeldTrust ledgers, journals and three-way reconciliation reports. | Has a placeTransactions and balances for look-up; it is not a trust accounting system. | Exported in full |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger with chart of accounts, bank feeds, accounts payable and cheque printing. | Has a placeGeneral ledger journals and balances, where the source held them. | Exported in full |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields can be used as merge fields in documents. | Has a placeAs added columns, or a table of field names and values. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | HeldTemplates are Word documents using merge fields downloaded from CosmoLex. | Has a place in partPrecedent files can be stored; automation does not run here. | Exported with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partIntake forms are included; the vendor also describes lead tracking. | 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 CosmoLex.
- 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.
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 CosmoLex 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 CosmoLex 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.
CosmoLex 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 CosmoLex will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving CosmoLex
Leaving CosmoLex is rarely just a practice management change. For most firms it is also the day their accounting system changes, since the general ledger, bank reconciliations and trust records are all inside. The matters and documents are planned in the usual way. A harder conversation is the one with the bookkeeper and accountant about where the books go next and on what date.
One ledger for everything
Billing posts straight to the general ledger, on a cash or accrual basis the firm chose at set-up. The books are not in a separate package that carries on unchanged. A destination with lighter accounting means a new package for the books, and trial balances from both are compared at the cutover date.
Reconciliations stay behind
Bank feeds, matched transactions and completed reconciliation statements are a record of work done, not data another system can load. Before cutover the firm runs and saves the reconciliation and three-way reports for every period it may be asked about, and the read-only copy of CosmoLex is kept as the fall-back record.
Inactive means settled
A matter can only be made inactive once its trust funds are disbursed, and on accrual accounting once its receivable is cleared. So an active matter is not always a live one. Some are finished files still holding money. They are listed for the firm, because the destination will treat them as open.
Emails tagged by address
Forwarded emails are tagged to a matter when the sender or recipient matches an email address on the client record, and land in a Tagged folder. Where there is no match, or more than one, the email waits for someone to file it. That untagged pile is either cleared or knowingly left behind before extraction.
Law society records in Canada
The Canadian edition produces law society compliance reports such as the clients’ general journal and general receipts journal. A Canadian firm needs those reports complete to the cutover date and stored where they can be produced on request. The destination’s own reports only start from the opening balances.
Where it is going
Arriving in Microsoft SQL Server
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.
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.
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.
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.
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.
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.
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.
Analysis
We read what CosmoLex holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything CosmoLex holds is in scope unless you take it out.
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.
Trial export
The data is written to Microsoft SQL Server as a trial and checked against CosmoLex: record counts, totals where CosmoLex holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in CosmoLex, the export is run a final time and checked again. There is nothing to go live. CosmoLex 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 CosmoLex 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 CosmoLex 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.
- 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
CosmoLex to Microsoft SQL Server: what firms ask
We are on CosmoLex Classic and are being moved to NextGen. Should we wait before changing systems?
It makes little difference to the data. The vendor describes NextGen as the same core functions with a new interface, and the firm’s records carry over. If a move away is already decided, the analysis can be done on whichever version the firm is using on the day.
Can our Word templates be reused?
The documents themselves can. CosmoLex templates are ordinary Word files that use mail merge fields taken from a CosmoLex field list. In a new system the wording and layout survive, and each merge field is replaced with the destination’s equivalent. Fields based on custom data take the longest to match.
How far back does the financial history go across?
That is a choice. Some destinations accept historic invoices, payments and trust transactions as records. Others start from opening balances, with older detail left in the read-only CosmoLex copy and in saved reports. Whichever is chosen, a complete trial load is run first so the trust and ledger figures can be agreed before the real cutover.
Does the copy in Microsoft SQL Server hold trust ledgers from CosmoLex?
Yes. Transactions and balances for look-up; it is not a trust accounting system. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in CosmoLex as at the export date.
Does everything in CosmoLex have a place in Microsoft SQL Server?
On paper, yes: each kind of record CosmoLex holds has a place in Microsoft SQL Server. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.
What has to be decided before CosmoLex 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. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from CosmoLex and into Microsoft SQL Server
Other destinations from CosmoLex
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.
CosmoLex and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.
Moving from CosmoLex 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.