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

Data migration route

Partner for Windows (P4W) to Litify migration

Partner for Windows (P4W) 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.

FromPartner for Windows (P4W)Server
  1. Matters: Carried across
  2. Documents: Carried across
  3. Tasks: Carried across
  4. Time and expenses: Carried across
  5. Emails: Carried with mapping
  6. Billing: Carried with mapping
  7. Templates: Carried with mapping
  8. Contacts: Confirmed in the analysis
  9. Notes: Confirmed in the analysis
  10. Calendar: Confirmed in the analysis
  11. Trust money: Confirmed in the analysis
  12. Firm accounts: Confirmed in the analysis
  13. Custom fields: Confirmed in the analysis
  14. Intake: Confirmed in the analysis
ToLitifyCloud
  • 4 carried
  • 3 mapped
  • 7 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Partner for Windows (P4W) to Litify

Each row is a kind of record Partner for Windows (P4W) holds, whether Litify has a place for it, and what is planned. On this route four kinds of record carry across, three kinds need mapping and seven kinds are confirmed in the analysis.

Records in Partner for Windows (P4W) and their place in Litify
RecordIn Partner for Windows (P4W)In LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters, with flexible case screens.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersTo be confirmedHas a placeLoaded as parties and connected by roles.Confirmed in the analysis
DocumentsFiles stored in or linked from the systemHeldSaved against client and matter; many file types, including video.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeldRelated emails are captured to the matter.Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeCalendar events on the matter.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partAutomated processes, warnings and reminders.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldIncludes time spent producing documents.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldHas 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 balancesHeldClient ledgers within the integrated accounts.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldPurchase ledgers and office accounts in the same database.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCustom fields are created before loading.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldTemplates with optional clauses, assembled through a wizard.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas 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 Partner for Windows (P4W).
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 Partner for Windows (P4W) 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 Partner for Windows (P4W), and kept as the record of what was billed and held.

Partner for Windows (P4W) 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

Having cases and accounts in one SQL database is convenient for extraction and demanding for reconciliation: every matter’s documents, time and ledgers are tied together, and all of it has to agree on the other side. Firms that use it for volume work can have very large numbers of matters, and deciding which of them move is the first real decision.

  1. One database for everything

    Case management and financial management share a single SQL database. A matter’s documents, time, bills and client ledger are held in the same place. That gives one consistent copy to work from. It also means the trial load can be checked end to end, matter by matter, against P4W’s own reports.

  2. Volume and bulk work

    The vendor describes P4W as suited to high-volume environments, with bulk processing as an option. Firms doing volume conveyancing, claims or recoveries accumulate very large numbers of small matters. Loading every one is rarely sensible. Closed matters past a chosen date usually stay in the archive, with their documents retrievable on request.

  3. Slips and postings

    Accounts work in P4W begins with a slip, which goes through approval before it is posted, billed or receipted. At cutover there may be slips raised but not yet approved. They are cleared or cancelled during the freeze, so the ledgers that are extracted contain only posted entries and agree with the bank.

  4. Bundles and portal submissions

    P4W can build electronic bundles and submit directly to government portals, including the MoJ, SDLT and Land Registry. Completed bundles are documents and move. Submissions already made are history. Any claim or application part-way through a portal process at cutover is listed so it is finished from the old system.

  5. Hosted or on premise

    A firm may run P4W on its own servers or have it hosted by the vendor. On premise, the database and documents are copied with the firm’s IT team. Hosted, the copy is requested from OneAdvanced. The answer also affects the fall-back: a read-only copy needs somewhere to run after the hosting ends.

More about moving off Partner for Windows (P4W)

Where it is going

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.

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

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

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

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

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

More about moving into Litify

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 Partner for Windows (P4W) and checking each trial against Partner for Windows (P4W).

  1. Analysis

    We read what Partner for Windows (P4W) 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.

  2. Clean-up

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

  3. Trial load

    The data is loaded into Litify as a trial and checked against Partner for Windows (P4W): record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Partner for Windows (P4W) 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 Partner for Windows (P4W) as at the cutover date. Partner for Windows (P4W) 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 Partner for Windows (P4W) 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 fromPartner for Windows (P4W)
Moving toLitify

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 Partner for Windows (P4W) 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.

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

Partner for Windows (P4W) to Litify: what firms ask

We have a very large number of closed matters. Do they all have to move?

No. The firm can set a cut-off. Matters closed before it stay in a read-only copy of P4W or an export of their documents, and everything after it moves. The cut-off follows the firm’s retention policy and how often old files are reopened. Our analysis gives counts for several possible dates so the choice is made on numbers.

Will our workflows and starter kits carry over?

No. Workflows built in P4W, including those from kits such as the Residential Conveyancing Starter Kit, run only in P4W. The documents they produced move with the matters. Processes are rebuilt in the destination’s workflow tool, starting with the highest-volume work types, and tested on trial data before go-live.

Do client ledgers come across with their postings?

Each matter’s client ledger balance is loaded and reconciled to P4W’s reports at the cutover date. Whether individual postings can follow depends on the destination. Where they cannot, a ledger printout for every open matter is saved to its file, and the complete history remains in the archived database.

Do trust balances in Partner for Windows (P4W) 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 Partner for Windows (P4W) 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 Partner for Windows (P4W) have a place in Litify?

Most of it does on paper. Contacts, notes, calendar entries, trust ledgers, the firm’s accounts, custom fields 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 Partner for Windows (P4W) data is loaded into Litify?

Emails, billing records and templates are carried with mapping, so each mapping is agreed with you first. Contacts, notes, calendar entries, trust ledgers, the firm’s accounts, custom fields 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

Partner for Windows (P4W) and Litify are the names and marks of their owners, used here only to identify the two systems.

Moving from Partner for Windows (P4W) 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.