Data migration route
Client Profiles to Litify migration
Client Profiles is a server-based practice management system, and Litify is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.
Client ProfilesServer- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Intake: Confirmed in the analysis
LitifyCloud- 6 carried
- 3 mapped
- 5 to confirm
What moves
What moves from Client Profiles to Litify
Each row is a kind of record Client Profiles holds, whether Litify has a place for it, and what is planned. On this route six kinds of record carry across, three kinds need mapping and five kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCalled cases; screens and numbering are set per law type. | Has a placeMatters, by case type. | Carried across |
| ContactsClients, other parties and referrers | HeldHeld in the Card File, with categories, custom tabs and pick lists. | Has a placeLoaded as parties and connected by roles. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldCase documents are kept in a History directory on the server; scanned pages may sit elsewhere. | Has a placeLoaded to the document component and attached to matters. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partReleases from 2014 integrate with Outlook Tasks and the CompuLaw court rules database. | Has a placeCalendar events on the matter. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTo-do packages set up per law type. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime slips, which can be released to a billing system. | Has a placeTime entries on the matter. | Carried across |
| BillingInvoices, payments and debtor balances | Held in partThrough the suite’s financial system, Profiles Financial or Profiles Plaintiff. | Has a place in partBilling is part of the product. Loading past invoices is scoped in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | Held in partTrust and escrow are in the suite’s financial system. | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | Held in partGeneral ledger and payables are in the suite’s financial system. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldCustom information screens and custom tabs. | Has a placeCustom fields are created before loading. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldMerge documents created from templates. | Has a place in partTemplates are rebuilt in Litify’s document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeLoaded as intakes. | Confirmed in the analysis |
What the plans mean
- Carried across
- Litify has a place for this kind of record. It is loaded there and checked against Client Profiles.
- Carried with mapping
- Litify 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.
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
Matters become cases. The ledgers need a home.
Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Litify. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.
Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from Client Profiles has to be given a case type in Litify, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Litify is exported as reports and ledgers the firm can open without Client Profiles, and kept as the record of what was billed and held.
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. Litify 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
Leaving Client Profiles
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Litify
Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.
The design comes first
Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.
One party, many roles
Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.
Open enquiries load as intakes
Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.
Documents load after records
Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.
Validation rules reject bad rows
A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Litify says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Client Profiles and checking each trial against Client Profiles.
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 Litify. Anything with no place there comes across as a note or stays behind, and you see which before the move.
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.
Trial load
The data is loaded into Litify as a trial and checked against Client Profiles: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Client Profiles are frozen for an agreed window, the data is collected a final time and Litify goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in Client Profiles as at the cutover date. 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
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 Client Profiles holds
What is in it, how its records link, and where each piece would sit in Litify. 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
Setting up Litify
Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.
A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.
Set-up decisions in Litify
- Define intake questionnaires and the rules for conversion
- Set case types, matter stages and page layouts
- Build matter plans that create tasks at each stage
- Design document folders and generation templates per case type
- Configure user roles and sharing for restricted matters
- Decide on timekeeping, billing and accounting integrations
Questions
Client Profiles to Litify: 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 Litify?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Client Profiles before the plan is fixed. If Litify turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
Does everything in Client Profiles have a place in Litify?
Most of it does on paper. Emails, notes, trust ledgers, the firm’s accounts and intake records could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Litify is kept as a readable archive, and you see which before the move.
What has to be decided before Client Profiles data is loaded into Litify?
Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, trust ledgers, the firm’s accounts 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.
Other routes
Other routes from Client Profiles and into Litify
Other destinations from Client Profiles
Other systems that move into Litify
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.
Client Profiles and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from Client Profiles to Litify?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.