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

Data migration route

Partner for Windows (P4W) to Gladiate migration

Partner for Windows (P4W) is a server-based practice management system, and Gladiate is a cloud case management system for personal injury work. 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. Templates: Carried with mapping
  5. Contacts: Confirmed in the analysis
  6. Emails: Confirmed in the analysis
  7. Notes: Confirmed in the analysis
  8. Calendar: Confirmed in the analysis
  9. Time and expenses: Confirmed in the analysis
  10. Billing: 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
ToGladiateCloud
  • 3 carried
  • 1 mapped
  • 10 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Partner for Windows (P4W) to Gladiate

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

Records in Partner for Windows (P4W) and their place in Gladiate
RecordIn Partner for Windows (P4W)In GladiateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters, with flexible case screens.Has a placePersonal injury cases.Carried across
ContactsClients, other parties and referrersTo be confirmedHas a placeClients, leads and referral sources.Confirmed in the analysis
DocumentsFiles stored in or linked from the systemHeldSaved against client and matter; many file types, including video.Has a placeFiled to the firm’s folder structure.Carried across
EmailsEmails saved to matters or to the storeHeldRelated emails are captured to the matter.To be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeEvents sync with Outlook and Google Calendar.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partAutomated processes, warnings and reminders.Has a placeTasks and task plans.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldIncludes time spent producing documents.To be confirmedConfirmed in the analysis
BillingInvoices, payments and debtor balancesHeldTo be confirmedConfirmed in the analysis
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 confirmedTo be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeldTemplates with optional clauses, assembled through a wizard.Has a place in partFirm templates are set up again in Gladiate. Old templates are not converted.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeLeads and client sign-up.Confirmed in the analysis

What the plans mean

Carried across
Gladiate has a place for this kind of record. It is loaded there and checked against Partner for Windows (P4W).
Carried with mapping
Gladiate 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 Gladiate. 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 Gladiate, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Gladiate 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. Gladiate 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

Gladiate is a destination for personal injury firms, and what it expects is injury data: a client, an incident, coverage, providers and a case status. Loading a firm into it means shaping the old system’s records into that pattern and preparing the templates, task plans and folder structure that the vendor’s onboarding asks each firm to supply.

  1. Injury fields come first

    Coverage, liability and medical details are what the product is designed to put in front of staff. In the old system they may be in custom fields, notes or a spreadsheet. They are pulled into columns during the analysis, so a loaded case shows its insurer and policy details and not an empty panel.

  2. Templates and task plans

    The vendor’s onboarding has each firm set up its own document templates, task plans, litigation deadlines and questionnaires. These are prepared from what the firm uses now. Merge fields in old templates are replaced with Gladiate’s, and task plans are written down stage by stage before anyone builds them.

  3. A folder structure per case

    Documents are filed in a folder structure the firm defines. The old system’s folders or categories are mapped to it once, and every case is loaded to the same pattern. Files with no clear category go to a holding folder on the case and are listed, not scattered.

  4. What it may not hold

    Time records, invoices and trust ledgers are not described on the vendor’s public pages. A firm that needs those carried over has it confirmed in the analysis. If there is no place for them, balances stay in the accounting package and the detailed history is kept in the old system, read only.

More about moving into Gladiate

How NewLaw runs it

Four steps, in this order.

No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Gladiate, they get a rehearsed cutover of their own.

  1. Analysis

    We read what Partner for Windows (P4W) holds and how it is organised, then agree with you where each kind of record will sit in Gladiate. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into Gladiate and checked against Partner for Windows (P4W): record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    After a short freeze on changes in Partner for Windows (P4W), a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. 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 toGladiate

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

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

Gladiate is delivered ready for injury work, so set-up is about making it the firm’s own. The vendor’s onboarding covers templates, task plans, folder structure, litigation deadlines and client questionnaires. Each of those is a decision the firm has to make, and it goes faster when current practice has been written down beforehand.

Set-up decisions in Gladiate

  • Set up and test the firm’s document templates
  • Write task plans for each stage of a case
  • Agree one folder structure for case documents
  • Enter litigation deadlines for the firm’s jurisdictions
  • Prepare client questionnaires, surveys and scheduled case updates
  • Connect Outlook or Google calendars for two-way sync

Questions

Partner for Windows (P4W) to Gladiate: 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 Gladiate?

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

Most of it does on paper. Contacts, emails, notes, calendar entries, time entries, billing records, 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 Gladiate 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 Gladiate?

Templates are carried with mapping, so each mapping is agreed with you first. Contacts, emails, notes, calendar entries, time entries, billing records, trust ledgers, the firm’s accounts, custom fields and intake records are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

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

Moving from Partner for Windows (P4W) to Gladiate?

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

We reply within one business day.