Data migration route
Partner for Windows (P4W) to Smokeball migration
Partner for Windows (P4W) is a server-based practice management system, and Smokeball is one that runs on the desktop and keeps its data in its maker’s cloud. Both run a whole practice, so this is a full move, and the financial records set the timetable.
Partner for Windows (P4W)Server- Matters: Carried across
- Documents: Carried across
- Emails: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Billing: Carried across
- Trust money: Carried with mapping
- Templates: Carried 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
SmokeballDesktop and cloud- Firm accounts: Kept as a readable archive
- 6 carried
- 2 mapped
- 5 to confirm
- 1 archived
What moves
What moves from Partner for Windows (P4W) to Smokeball
Each row is a kind of record Partner for Windows (P4W) holds, whether Smokeball has a place for it, and what is planned. On this route six kinds of record carry across, two kinds need mapping, one kind has no place in Smokeball and is archived 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 placeEach needs a Smokeball matter type; leads import alongside matters. | Carried across |
| ContactsClients, other parties and referrers | To be confirmed | Has a placeMatter roles import on the Grow and Prosper+ plans only. | Confirmed in the analysis |
| DocumentsFiles stored in or linked from the system | HeldSaved against client and matter; many file types, including video. | Has a placeFiles and folders import into a matter with the folder structure kept. | Carried across |
| EmailsEmails saved to matters or to the store | HeldRelated emails are captured to the matter. | Has a placeKept in the matter with other files. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeAs memos; not importable on the Bill plan. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeCalendar events and critical dates; plan limits apply. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held in partAutomated processes, warnings and reminders. | Has a placeNot importable on the Bill plan. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldIncludes time spent producing documents. | Has a placeUnbilled time, fee and expense entries, with activity codes. | Carried across |
| BillingInvoices, payments and debtor balances | Held | Has a placeInvoices and billed invoice entries are on the import list. | Carried across |
| Trust moneyTrust or client account ledgers and balances | HeldClient ledgers within the integrated accounts. | Has a place in partMatter account balances load as opening balances; past transactions are not on the import list. | Carried with mapping |
| Firm accountsGeneral ledger, office account and payables | HeldPurchase ledgers and office accounts in the same database. | No placeNo general ledger; the firm’s books stay in an accounting package. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a place in partValues need a matching field in the matter type’s layouts. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldTemplates with optional clauses, assembled through a wizard. | Has a placeFirm precedents are rebuilt as Smokeball templates. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeLeads are a record type of their own and can be converted to matters. | Confirmed in the analysis |
What the plans mean
- Carried across
- Smokeball has a place for this kind of record. It is loaded there and checked against Partner for Windows (P4W).
- Carried with mapping
- Smokeball 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.
- Kept as a readable archive
- Smokeball has no place for it. It is exported in a format that opens without Partner for Windows (P4W) and handed to the firm as a read-only archive.
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
The whole practice moves, accounts included.
A move between two practice management systems is the widest kind there is. Partner for Windows (P4W) and Smokeball each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.
The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with Partner for Windows (P4W)’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.
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. Smokeball 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 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 Smokeball
Smokeball has a data import tool that reads spreadsheets of staff, contacts, matters, balances, unbilled time, invoices, memos, tasks and calendar events. Some of those are only available on the higher plans. Documents are brought in separately, with their folders. Before the first trial, every incoming matter is given a Smokeball matter type, since nothing else about the matter can be placed without one.
Every matter needs a type
Smokeball’s matter types are specific to an area of law and a state or jurisdiction, and each brings its own fields. The old system’s matter types are mapped to them one by one. It is worth getting right the first time: changing a matter’s type later can drop the details held in layouts the new type does not have.
The plan decides what loads
Matter roles, tags, critical dates and archive details import only on the Grow and Prosper+ plans. Memos, tasks and calendar events do not import on the Bill plan. The firm’s plan is confirmed before the mapping is written, so nobody maps the other side’s solicitor to a role that the subscription cannot hold.
Leave auto-numbering until after
Smokeball’s guidance for firms still bringing matters in is to wait before setting up automatic Internal References. Imported matters arrive with the numbers they already had. Once the load is accepted, the reference format and the counter’s starting number are set so the first new matter follows on from the last old one.
Documents arrive by folder
Importing a folder into a matter keeps its subfolders, and default folders can also be defined per matter type. The firm decides which wins where they differ: the old structure as it was, or its new standard layout with old folders mapped into it.
An opening balance per matter
Matter account balances are on the import list, along with unbilled time and expenses, invoices and billed invoice entries. Past trust transactions are not on that list. The trust position is therefore loaded as an opening balance for each matter and rehearsed on a full trial, with the transaction history kept in the old system.
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.
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 Smokeball. 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 Partner for Windows (P4W), before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Smokeball as a trial and checked against Partner for Windows (P4W): record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Partner for Windows (P4W) are frozen for an agreed window, the data is collected a final time and Smokeball 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. 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
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 Smokeball. 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 Smokeball
Loaded data is not yet a working system. This is what NewLaw sets up in Smokeball, beyond the migration, so that people can work in it from the first day.
A Smokeball set-up is partly on the firm’s PCs and partly in firm settings. The desktop app and its Word and Outlook add-ins go on each Windows machine. In settings, the firm chooses the matter types it will use, defines default folders for each and sets its numbering. Trust accounts and the accounting connection are configured before the first invoice is raised.
Set-up decisions in Smokeball
- Matter types in use, with default document folders for each
- Internal Reference format and the starting number for new matters
- Trust account details and the link to the accounting package
- Staff roles and permissions, including who sees billing and trust
- Firm precedents and letterhead rebuilt as Smokeball templates
- Desktop app, Word and Outlook add-ins on every PC
Questions
Partner for Windows (P4W) to Smokeball: 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 Smokeball?
In part. Matter account balances load as opening balances; past transactions are not on the import list. The analysis sets out which trust records have a place in Smokeball and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.
What happens to records Smokeball has no place for?
On this route that is the firm’s accounts. They are exported from Partner for Windows (P4W) in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.
What has to be decided before Partner for Windows (P4W) data is loaded into Smokeball?
Trust ledgers and templates are carried 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 sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from Partner for Windows (P4W) and into Smokeball
Other destinations from Partner for Windows (P4W)
Other systems that move into Smokeball
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 Smokeball are the names and marks of their owners, used here only to identify the two systems.
Moving from Partner for Windows (P4W) to Smokeball?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.