Data migration route
Partner for Windows (P4W) data to Microsoft SQL Server
Partner for Windows (P4W) is a server-based practice management system, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what Partner for Windows (P4W) holds and keeps it readable and open to queries.
Partner for Windows (P4W)Server- Matters: Exported in full
- Tasks: Exported in full
- Time and expenses: Exported in full
- Billing: Exported in full
- Trust money: Exported in full
- Firm accounts: Exported in full
- Documents: Exported with mapping
- Emails: Exported with mapping
- Templates: Exported with mapping
- Contacts: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Intake: Confirmed in the analysis
Microsoft SQL ServerServer- 6 carried
- 3 mapped
- 5 to confirm
What moves
What moves from Partner for Windows (P4W) to Microsoft SQL Server
Each row is a kind of record Partner for Windows (P4W) holds, whether Microsoft SQL Server 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 | HeldClients and matters, with flexible case screens. | Has a placeA table of matters linked to clients, parties and fee earners. | Exported in full |
| ContactsClients, other parties and referrers | To be confirmed | Has a placePeople and companies, with their roles on each matter. | Confirmed in the analysis |
| DocumentsFiles stored in or linked from the system | HeldSaved against client and matter; many file types, including video. | Has a place in partAs files in folders with an index table; storing files in the database is possible. | Exported with mapping |
| EmailsEmails saved to matters or to the store | HeldRelated emails are captured to the matter. | Has a place in partAs message files with an index table, or as rows of header fields. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeRows of text linked to matters and contacts. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeRows of appointments and key dates; nothing displays them as a calendar. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held in partAutomated processes, warnings and reminders. | Has a placeRows with assignee, due date and status. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | HeldIncludes time spent producing documents. | Has a placeTime and expense rows with rates and billed status. | Exported in full |
| BillingInvoices, payments and debtor balances | Held | Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | HeldClient ledgers within the integrated accounts. | Has a placeTransactions and balances for look-up; it is not a trust accounting system. | Exported in full |
| Firm accountsGeneral ledger, office account and payables | HeldPurchase ledgers and office accounts in the same database. | Has a placeGeneral ledger journals and balances, where the source held them. | Exported in full |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeAs added columns, or a table of field names and values. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldTemplates with optional clauses, assembled through a wizard. | Has a place in partPrecedent files can be stored; automation does not run here. | Exported with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeEnquiry rows, where the source recorded them. | Confirmed in the analysis |
What the plans mean
- Exported in full
- Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against Partner for Windows (P4W).
- Exported with mapping
- Microsoft SQL Server 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
Not a new system. A complete copy the firm can query.
Writing Partner for Windows (P4W) out to Microsoft SQL Server is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.
What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Partner for Windows (P4W) as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.
Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Partner for Windows (P4W) stays untouched until the copy in Microsoft SQL Server has been checked.
Where the data is now
Leaving Partner for Windows (P4W)
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Microsoft SQL Server
There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.
Restored copy or rebuilt schema
Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.
No screens come with it
A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.
Documents sit beside the database
Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.
The edition follows the size
A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.
Backups and a test restore
An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what Partner for Windows (P4W) holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Partner for Windows (P4W) holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to Microsoft SQL Server as a trial and checked against Partner for Windows (P4W): record counts, totals where Partner for Windows (P4W) holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in Partner for Windows (P4W), the export is run a final time and checked again. There is nothing to go live. Partner for Windows (P4W) is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
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
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 Partner for Windows (P4W) holds
What is in it, how its records link, and where each piece would sit in Microsoft SQL Server. 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
Structure, permissions and handover
Microsoft SQL Server is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.
What is agreed and set up
- Server, instance and edition agreed with the IT provider
- Read-only logins and roles for named staff
- Views for matter, ledger, time and document look-ups
- Backup schedule and who tests a restore
- Plain names and descriptions for tables and columns
- Excel or Power BI connected for reporting
Questions
Partner for Windows (P4W) to Microsoft SQL Server: 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.
Does the copy in Microsoft SQL Server hold trust ledgers from Partner for Windows (P4W)?
Yes. Transactions and balances for look-up; it is not a trust accounting system. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Partner for Windows (P4W) as at the export date.
Does everything in Partner for Windows (P4W) have a place in Microsoft SQL Server?
Most of it does on paper. Contacts, notes, calendar entries, 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 Microsoft SQL Server is kept as a readable archive, and you see which before the move.
What has to be decided before Partner for Windows (P4W) is written out to Microsoft SQL Server?
Documents, emails and templates are exported with mapping, so each mapping is agreed with you first. Contacts, notes, calendar entries, custom fields and intake records are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from Partner for Windows (P4W) and into Microsoft SQL Server
Other destinations from Partner for Windows (P4W)
Other systems that move into Microsoft SQL Server
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.
Partner for Windows (P4W) and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.
Moving from Partner for Windows (P4W) to Microsoft SQL Server?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.