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

Data migration route

Client Profiles to SimpleLaw migration

Client Profiles is a server-based practice management system, and SimpleLaw is a cloud one. Both run a whole practice, so this is a full move, and the financial records set the timetable.

FromClient ProfilesServer
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Calendar: Carried across
  5. Tasks: Carried across
  6. Time and expenses: Carried across
  7. Billing: Carried with mapping
  8. Trust money: Carried with mapping
  9. Custom fields: Carried with mapping
  10. Templates: Carried with mapping
  11. Emails: Confirmed in the analysis
  12. Notes: Confirmed in the analysis
  13. Intake: Confirmed in the analysis
ToSimpleLawCloud
  1. Firm accounts: Kept as a readable archive
Readable archiveNo place in SimpleLaw
  • 6 carried
  • 4 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 SimpleLaw

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

Records in Client Profiles and their place in SimpleLaw
RecordIn Client ProfilesIn SimpleLawWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled cases; screens and numbering are set per law type.Has a placeCarried across
ContactsClients, other parties and referrersHeldHeld in the Card File, with categories, custom tabs and pick lists.Has a placeAs leads, clients or other contacts in the CRM.Carried across
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 placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedTo be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partReleases from 2014 integrate with Outlook Tasks and the CompuLaw court rules database.Has a placeCarried across
TasksTo-dos and workflow steps assigned to peopleHeldTo-do packages set up per law type.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTime slips, which can be released to a billing system.Has a placeCarried across
BillingInvoices, payments and debtor balancesHeld in partThrough the suite’s financial system, Profiles Financial or Profiles Plaintiff.Has a place in partInvoices are created in the product; loading invoice history is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeld in partTrust and escrow are in the suite’s financial system.Has a place in partTrust balances are supported; history depth is confirmed in the analysis.Carried with mapping
Firm accountsGeneral ledger, office account and payablesHeld in partGeneral ledger and payables are in the suite’s financial system.No placeGeneral ledger stays in QuickBooks or another accounting package.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldCustom information screens and custom tabs.Has a placeCarried with mapping
TemplatesPrecedents, document templates and automationHeldMerge documents created from templates.Has a place in partTemplates are rebuilt using SimpleLaw’s own automation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeLeads and intake forms.Confirmed in the analysis

What the plans mean

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

The whole practice moves, accounts included.

A move between two practice management systems is the widest kind there is. Client Profiles and SimpleLaw each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.

The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with Client Profiles’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.

Client Profiles runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. SimpleLaw is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

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

Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.

  1. Lead, client or contact

    A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.

  2. Billing type on each matter

    Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.

  3. Storage chosen before loading

    If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.

  4. Custom fields named for templates

    Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.

  5. Portal access client by client

    The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.

More about moving into SimpleLaw

How NewLaw runs it

Four steps, in this order.

Trust money moves on this route, so the trust cutover gets a rehearsal of its own.

  1. Analysis

    We read what Client Profiles holds and how its records link, then agree with you, field by field, where each piece will sit in SimpleLaw. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Client Profiles, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into SimpleLaw as a trial and checked against Client Profiles: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Client Profiles are frozen for an agreed window, the data is collected a final time and SimpleLaw goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. Client Profiles 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 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 toSimpleLaw

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

Setting up SimpleLaw

Loaded data is not yet a working system. This is what NewLaw sets up in SimpleLaw, beyond the migration, so that people can work in it from the first day.

The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.

Set-up decisions in SimpleLaw

  • Labels for documents, activities, expenses and contact IDs
  • Custom fields and intake forms for each practice area
  • Document templates and the attorney-client agreement
  • Workflows for case types that follow a standard process
  • User permission sets and client portal visibility
  • QuickBooks connection and the online payment processor

Questions

Client Profiles to SimpleLaw: 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.

Do trust balances in Client Profiles have a place in SimpleLaw?

In part. Trust balances are supported; history depth is confirmed in the analysis. The analysis sets out which trust records have a place in SimpleLaw and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

What happens to records SimpleLaw has no place for?

On this route that is the firm’s accounts. 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 data is loaded into SimpleLaw?

Billing records, trust ledgers, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails, notes and intake records are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.

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 SimpleLaw are the names and marks of their owners, used here only to identify the two systems.

Moving from Client Profiles to SimpleLaw?

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

We reply within one business day.