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

Data migration route

CosmoLex to Server drives migration

CosmoLex is a cloud practice management system, and Server drives are plain files on equipment the firm controls. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

FromCosmoLexCloud
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Notes: Carried with mapping
  4. Templates: Carried with mapping
ToServer drivesFiles
  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. Trust money: Kept as a readable archive
  8. Firm accounts: Kept as a readable archive
  9. Custom fields: Kept as a readable archive
  10. Intake: Kept as a readable archive
Readable archiveNo place in Server drives
  • 1 carried
  • 3 mapped
  • 10 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from CosmoLex to Server drives

Each row is a kind of record CosmoLex holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping and ten kinds have no place in Server drives and are archived.

Records in CosmoLex and their place in Server drives
RecordIn CosmoLexIn Server drivesWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldEach has a Matter File #, an area of law and a matter owner.No placeA matter becomes a folder; its details survive only in an index file.Kept as a readable archive
ContactsClients, other parties and referrersHeldClients and other contacts; payees for accounts payable are a separate list.No placeCan be kept only as an exported spreadsheet.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeldBuilt-in storage, or OneDrive, Google Drive, Dropbox, Box or NetDocuments linked by matter.Has a placeFiles in folders, named and dated during the load.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails sent to the firm’s forwarding address are tagged to matters by sender or recipient.Has a place in partAs .msg or .eml files in each matter’s correspondence folder.Carried with mapping
NotesFile notes, matter notes and contact notesHeldHas a place in partAs a text or PDF file per matter, not as separate records.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldNo placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTask workflows can be loaded into new or existing matters.No placeKept as a readable archive
Time and expensesTime and expense entries, billed and unbilledHeldEntries are called timecards.No placeOnly as exported reports or spreadsheets.Kept as a readable archive
BillingInvoices, payments and debtor balancesHeldHas a place in partInvoices as PDF files; no ledger.Kept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldTrust ledgers, journals and three-way reconciliation reports.No placeOnly as exported ledger reports kept as files.Kept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger with chart of accounts, bank feeds, accounts payable and cheque printing.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldCustom fields can be used as merge fields in documents.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationHeldTemplates are Word documents using merge fields downloaded from CosmoLex.Has a place in partPrecedents as Word files; merge fields tied to the old system stop working.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partIntake forms are included; the vendor also describes lead tracking.No placeKept as a readable archive

What the plans mean

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

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

File storage has folders and files and nothing else. Moving from CosmoLex into Server drives 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 Server drives do 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 CosmoLex.

CosmoLex is hosted by its maker and Server drives sit 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 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.

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

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

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

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

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

More about moving off CosmoLex

Where it is going

Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.

  1. Agree the tree and the names

    A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.

  2. Budget the path length

    Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.

  3. Dates have to be set deliberately

    A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.

  4. Emails become message files

    Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.

  5. Keep an index beside the files

    A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.

More about moving into Server drives

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

    We read what CosmoLex holds and how it is organised, then agree with you where each kind of record will sit in Server drives. 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 Server drives and checked against CosmoLex: 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 CosmoLex, a final pass over a weekend picks up what changed since the trial. CosmoLex 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 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

Step 1 of 5: Start with the route

Moving fromCosmoLex
Moving toServer drives

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 CosmoLex holds

    What is in it, how its records link, and where each piece would sit in Server drives. 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

Server drives are 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 server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.

What is agreed and set up

  • Share and top-level folders for clients, precedents and administration
  • Security groups and folder permissions, with restricted matters separate
  • Drive letter mapped for every user at sign-in
  • Backup schedule and shadow copies for earlier versions
  • Written naming rule for client, matter and document names
  • Read-only area for closed matters and archived system exports

Questions

CosmoLex to Server drives: 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.

Do trust balances in CosmoLex have a place in Server drives?

No. Server drives do not keep trust ledgers. Only as exported ledger reports kept as files. Trust records from CosmoLex are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.

What happens to records Server drives have no place for?

On this route that is matters, contacts, calendar entries, tasks, time entries, billing records, trust ledgers, the firm’s accounts, custom fields and intake records. 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 data is loaded into Server drives?

Emails, notes and templates are carried with mapping, so each mapping is agreed with you first. 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

CosmoLex and Server drives are the names and marks of their owners, used here only to identify the two systems.

Moving from CosmoLex to Server drives?

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

We reply within one business day.