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

Data migration route

Client Profiles to Filevine migration

Client Profiles is a server-based practice management system, and Filevine is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.

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 with mapping
  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. Firm accounts: Confirmed in the analysis
  14. Intake: Confirmed in the analysis
ToFilevineCloud
  • 5 carried
  • 5 mapped
  • 4 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Client Profiles to Filevine

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

Records in Client Profiles and their place in Filevine
RecordIn Client ProfilesIn FilevineWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled cases; screens and numbering are set per law type.Has a placeLoaded as projects of a defined project type.Carried across
ContactsClients, other parties and referrersHeldHeld in the Card File, with categories, custom tabs and pick lists.Has a placeContact cards, linked to projects.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 placeDocs section with folders. Templated project folders can be set per type.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeHeld in the activity feed of the project.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeHeld as notes in the activity feed.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 placeDeadlines and calendar events.Carried 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 place in partNeeds the Billing product enabled.Carried with mapping
BillingInvoices, payments and debtor balancesHeld in partThrough the suite’s financial system, Profiles Financial or Profiles Plaintiff.Has a place in partNeeds the Billing product enabled.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 accounts sit in Payments by Filevine. Loading history 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.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom information screens and custom tabs.Has a placeCustom sections and fields per project type.Carried with mapping
TemplatesPrecedents, document templates and automationHeldMerge documents created from templates.Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a place in partLeads belong in Lead Docket, which passes signed clients to Filevine.Confirmed in the analysis

What the plans mean

Carried across
Filevine has a place for this kind of record. It is loaded there and checked against Client Profiles.
Carried with mapping
Filevine 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 Filevine. 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 Filevine, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Filevine 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. Filevine 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 Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.

  1. Project types before data

    Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.

  2. One contact card per person

    Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.

  3. Lists become collection items

    Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.

  4. History goes into the feed

    File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.

  5. Billing is a separate switch

    The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.

More about moving into Filevine

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 Filevine. 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 Filevine 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 Filevine 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 toFilevine

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

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

Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.

Set-up decisions in Filevine

  • Design project types, sections and fields for each practice area
  • Define phases and the tasks each phase should trigger
  • Build document templates that fill from project fields
  • Set teams, permissions and protected sections for restricted matters
  • Decide whether Billing and Payments are switched on
  • Connect Lead Docket so signed leads become projects

Questions

Client Profiles to Filevine: 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 Filevine?

In part. Trust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. The analysis sets out which trust records have a place in Filevine and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

Does everything in Client Profiles have a place in Filevine?

Most of it does on paper. Emails, notes, 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 Filevine 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 Filevine?

Time entries, billing records, trust ledgers, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, 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.

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

Moving from Client Profiles to Filevine?

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

We reply within one business day.