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

Data migration route

Client Profiles data to SQLite

Client Profiles is a server-based 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 Client Profiles holds and keeps it readable and open to queries.

FromClient ProfilesServer
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Calendar: Exported in full
  4. Tasks: Exported in full
  5. Time and expenses: Exported in full
  6. Billing: Exported in full
  7. Trust money: Exported in full
  8. Firm accounts: Exported in full
  9. Documents: Exported with mapping
  10. Custom fields: Exported with mapping
  11. Emails: Confirmed in the analysis
  12. Notes: Confirmed in the analysis
  13. Intake: Confirmed in the analysis
ToSQLiteFiles
  1. Templates: Kept as a readable archive
Readable archiveNo place in SQLite
  • 8 carried
  • 2 mapped
  • 3 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Client Profiles to SQLite

Each row is a kind of record Client Profiles holds, whether SQLite has a place for it, and what is planned. On this route eight kinds of record carry across, two kinds need mapping, one kind has no place in SQLite and is archived and three kinds are confirmed in the analysis.

Records in Client Profiles and their place in SQLite
RecordIn Client ProfilesIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled cases; screens and numbering are set per law type.Has a placeA matters table keyed by matter number.Exported in full
ContactsClients, other parties and referrersHeldHeld in the Card File, with categories, custom tabs and pick lists.Has a placeContacts and their roles on matters as linked tables.Exported in full
DocumentsFiles stored in or linked from the systemHeldCase documents are kept in a History directory on the server; scanned pages may sit elsewhere.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 storeTo be confirmedHas a place in partAs message files in folders, indexed in a table.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeA notes table linked to matters.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partReleases from 2014 integrate with Outlook Tasks and the CompuLaw court rules database.Has a placeA table of dated entries, with no calendar view.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldTo-do packages set up per law type.Has a placeA table of tasks and their status at the final date.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldTime slips, which can be released to a billing system.Has a placeA table of time and expense entries.Exported in full
BillingInvoices, payments and debtor balancesHeld in partThrough the suite’s financial system, Profiles Financial or Profiles Plaintiff.Has a placeInvoice and receipt tables; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeld in partTrust and escrow are in the suite’s financial system.Has a placeTrust transactions as rows, for look-up and not for accounting.Exported in full
Firm accountsGeneral ledger, office account and payablesHeld in partGeneral ledger and payables are in the suite’s financial system.Has a placeLedger journals as rows, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfHeldCustom information screens and custom tabs.Has a placeColumns added to the table they belonged to.Exported with mapping
TemplatesPrecedents, document templates and automationHeldMerge documents created from templates.No placePrecedent files are kept in folders, not in the database.Kept as a readable archive
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeAn enquiries table, where the source tracked them.Confirmed in the analysis

What the plans mean

Exported in full
SQLite has a place for this kind of record. It is loaded there and checked against Client Profiles.
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.
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
SQLite has no place for it. It is exported in a format that opens without Client Profiles 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 Client Profiles 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 Client Profiles 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.

Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Client Profiles stays untouched until the copy in SQLite has been checked.

Where the data is now

Plenty of firms still say Client Profiles when the screen in front of them says Total Office. It is the same system. A move off it means reading a SQL Server database, collecting case documents from a history folder on the server, and working out how each law type was set up, because every law type carries its own screens and fields.

  1. Law types shape everything

    Every case belongs to a law type, and the law type decides its summary screen, custom information screens, numbering and to-do packages. Field mapping is therefore done once per law type, not once for the firm. The rarely used law types need as much attention as the busy ones, since their fields are the least documented.

  2. Numbering follows a formula

    Case numbers can be typed by hand or built from a formula set per law type, such as a four-digit client number, a dash and a four-digit matter sequence. Old and new formats often sit side by side. The numbers are carried as they are, and the destination’s own numbering starts above the highest one in use.

  3. Parties are more than opponents

    A party here is anyone with a role in a case: doctors, judges and insurance companies as well as plaintiffs and defendants. Each comes from the Card File and has a category. Categories are mapped to contact roles in the new system, and people entered twice in the Card File are merged where they can be identified.

  4. Documents sit in History

    Case documents are stored in a History directory, normally under the shared CPWin folder, and scanned pages can be kept in a second location if space was short. Both are collected. The link from each file to its case is in the database, so the folders alone do not show what belongs where.

  5. Time may leave by export

    Time slips can be entered against a case and then released to a billing system, either the suite’s own financial side or a third-party product. Where the money sits depends on which the firm chose. That billing source is identified in the analysis and matched to cases on the case number.

More about moving off Client Profiles

Where it is going

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.

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

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

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

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

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

More about moving into SQLite

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.

  1. Analysis

    We read what Client Profiles holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Client Profiles holds is in scope unless you take it out.

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

  3. Trial export

    The data is written to SQLite as a trial and checked against Client Profiles: record counts, totals where Client Profiles holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in Client Profiles, the export is run a final time and checked again. There is nothing to go live. Client Profiles 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 Client Profiles 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 fromClient Profiles
Moving toSQLite

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 Client Profiles 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.

  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

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

Client Profiles to SQLite: what firms ask

Is Client Profiles the same as Aderant Total Office?

Yes. Aderant’s own announcements describe Total Office as formerly Client Profiles, and the administrator’s manual for Total Office still refers to CP and the CPWin folder. Older releases show the Client Profiles name on screen. The work of moving is the same under either name, and the release number is noted at the start.

What happens to our custom information screens?

Each custom screen is a set of fields added for a law type. Where the destination has custom fields, the ones in real use are recreated and filled. Screens the firm stopped using are listed with a count of how many cases have anything in them, and the firm decides which are worth recreating.

Do medical record requests come across?

The records request screens track requests for medical records on a case. Few systems outside personal injury have a matching feature. If the destination is built for injury work, requests are mapped to its own tracker. Otherwise they come across as dated notes on the case so the history is not lost.

Does the copy in SQLite hold trust ledgers from Client Profiles?

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 Client Profiles as at the export date.

What happens to records SQLite has no place for?

On this route that is templates. They are exported from Client Profiles 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 Client Profiles is written out to SQLite?

Documents and custom fields are exported with mapping, so each mapping is agreed with you first. Emails, notes and intake records are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.

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

Client Profiles and SQLite are the names and marks of their owners, used here only to identify the two systems.

Moving from Client Profiles 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.