Data migration route
CosmoLex data to SQLite
CosmoLex is a cloud practice management system, and SQLite is a store of data kept as files the firm holds. 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
SQLiteFiles- Templates: Kept as a readable archive
- 10 carried
- 3 mapped
- 1 archived
What moves
What moves from CosmoLex to SQLite
Each row is a kind of record CosmoLex holds, whether SQLite has a place for it, and what is planned. On this route ten kinds of record carry across, three kinds need mapping and one kind has no place in SQLite and is archived.
| 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 matters table keyed by matter number. | Exported in full |
| ContactsClients, other parties and referrers | HeldClients and other contacts; payees for accounts payable are a separate list. | Has a placeContacts and their roles on matters as linked tables. | 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 partListed in a table; the files themselves stay in folders beside the database. | 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 in folders, indexed in a table. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | Held | Has a placeA notes table linked to matters. | Exported in full |
| CalendarAppointments, court dates and deadlines | Held | Has a placeA table of dated entries, with no calendar view. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | HeldTask workflows can be loaded into new or existing matters. | Has a placeA table of tasks and their status at the final date. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | HeldEntries are called timecards. | Has a placeA table of time and expense entries. | Exported in full |
| BillingInvoices, payments and debtor balances | Held | Has a placeInvoice and receipt tables; 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 placeTrust transactions as rows, for look-up and not for accounting. | 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 placeLedger journals as rows, 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 placeColumns added to the table they belonged to. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | HeldTemplates are Word documents using merge fields downloaded from CosmoLex. | No placePrecedent files are kept in folders, not in the database. | Kept as a readable archive |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partIntake forms are included; the vendor also describes lead tracking. | Has a placeAn enquiries table, where the source tracked them. | Exported in full |
What the plans mean
- Exported in full
- SQLite has a place for this kind of record. It is loaded there and checked against CosmoLex.
- Exported with mapping
- SQLite holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
- Kept as a readable archive
- SQLite has no place for it. It is exported in a format that opens without CosmoLex 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
Not a new system. A complete copy the firm can query.
Writing CosmoLex out to SQLite 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 SQLite 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 SQLite
A SQLite archive suits a firm that wants the old system’s records kept, seldom consulted, and free of any server or subscription. Everything structured goes into one file. That simplicity moves the responsibility elsewhere: the file has no security of its own and no administrator watching it, so where it is stored and who can reach it are the real decisions.
One file, kept with the archive
Matters, contacts, time, invoices and trust transactions become tables in a single file. It is stored with the firm’s closed-matter records and can be copied like any document. A checksum recorded when the file is finalised lets anyone confirm, years later, that the copy they hold has not been altered, and the firm decides whether to keep one.
No logins inside the file
SQLite has no users or passwords. Anyone who can open the file can read every client’s ledger. Protection comes from where it is kept, such as a restricted folder or an encrypted volume, and that choice is the firm’s. It can suit an archive consulted by two people, and it is said plainly so nobody assumes otherwise.
Built for reading, not sharing
Only one program can write to the file at a time, and SQLite’s authors point people to a client/server database where many users share data over a network. A finished archive never meets that limit. It is the reason SQLite is used here for records that are closed and not for anything staff still update.
Documents stay outside it
Documents remain ordinary files in matter folders, and a table in the database lists each one with its matter, title, dates and path. Keeping them as files means they open with a double-click and can be handed to a client. The table is how a file is found by matter number instead of by guessing its name.
Someone has to open it
SQLite publishes its own command-line program for opening a database file, and other tools read the format too. None of that helps if nobody remembers how. Saved queries for the usual look-ups and a short note on which tool to use can sit in the same folder as the file, and the firm decides what it needs.
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 SQLite 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 SQLite 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 SQLite. 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
SQLite 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.
There is nothing to install on a server and nothing to license. The work is in making the file usable and safe to keep: naming it, documenting its tables, storing it where the firm’s records policy says archives go, and checking that a member of staff can open it and find a matter. Whether a second copy is held somewhere separate is the firm’s call.
What is agreed and set up
- File name, storage location and whether a second copy exists
- Whether a checksum is recorded for later verification
- Saved queries for matter, ledger and document look-ups
- Which tool staff will use to open the file
- Who may open the folder the file sits in
- Retention period and destruction date noted beside the file
Questions
CosmoLex to SQLite: 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 SQLite hold trust ledgers from CosmoLex?
Yes. Trust transactions as rows, for look-up and not for accounting. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in CosmoLex as at the export date.
What happens to records SQLite has no place for?
On this route that is templates. They are exported from CosmoLex 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 CosmoLex is written out to SQLite?
Documents, emails and custom fields 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 SQLite
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 SQLite are the names and marks of their owners, used here only to identify the two systems.
Moving from CosmoLex to SQLite?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.