Data migration route
Partner for Windows (P4W) to Sync.com migration
Partner for Windows (P4W) is a server-based practice management system, and Sync.com is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.
Partner for Windows (P4W)Server- Documents: Carried across
- Emails: 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
Sync.comCloud- Matters: Kept as a readable archive
- Tasks: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Trust money: Kept as a readable archive
- Firm accounts: Kept as a readable archive
- 1 carried
- 2 mapped
- 5 to confirm
- 6 archived
What moves
What moves from Partner for Windows (P4W) to Sync.com
Each row is a kind of record Partner for Windows (P4W) holds, whether Sync.com has a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping, six kinds have no place in Sync.com and are 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. | No placeA matter is a folder in Files or Vault. | Kept as a readable archive |
| ContactsClients, other parties and referrers | To be confirmed | No place | 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 within the path limit; some file types are skipped by the apps. | Carried across |
| EmailsEmails saved to matters or to the store | HeldRelated emails are captured to the matter. | Has a place in partMessage files such as .msg or .eml, filed in the matter’s folder. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place in partOnly as a document written out to the matter’s folder. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | No place | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held in partAutomated processes, warnings and reminders. | No place | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | HeldIncludes time spent producing documents. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | Held | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | HeldClient ledgers within the integrated accounts. | No place | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | HeldPurchase ledgers and office accounts in the same database. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | To be confirmed | No place | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldTemplates with optional clauses, assembled through a wizard. | Has a place in partPrecedents load as ordinary files. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | No place | Confirmed in the analysis |
What the plans mean
- Carried across
- Sync.com has a place for this kind of record. It is loaded there and checked against Partner for Windows (P4W).
- Carried with mapping
- Sync.com 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
- Sync.com 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
Out of the system, into folders the firm can read.
File storage has folders and files and nothing else. Moving from Partner for Windows (P4W) into Sync.com means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Sync.com does not allow in a name.
Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in Partner for Windows (P4W).
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. Sync.com 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 Sync.com
A firm that moves its files to Sync is usually doing so for confidentiality, and the load has to respect how the service is built to deliver it. Files are encrypted before they leave the computer. Nobody at Sync can look inside the account to confirm what arrived, so the checking is done from the firm’s side, against the list of what was sent.
Files or Vault
Open matters belong in Files, where they sync to the people working on them. Closed matters can go to Vault, which holds them in the cloud without putting a copy on every laptop. The firm supplies its open and closed matter lists so each folder is sent to the right side.
A 248 character path limit
Sync sets a maximum path length of 248 characters to stay compatible between Windows and Mac, and its apps skip anything longer. That is tighter than most systems a firm will be coming from. Folder names are shortened in the plan, and Sync’s own guidance favours a tree only a few levels deep.
What the apps leave out
The desktop apps do not upload shortcut files, temporary Office files or names containing a slash, and they warn against several other characters on Windows. A copy to Vault produces a transfer report listing what was skipped. That report is reconciled against the source file list after every load.
Permissions come from the top folder
Sharing is set on a folder and flows down to all of its contents. A matter that needs different access from the rest of a client’s work cannot simply sit one level down with tighter settings. It becomes its own shared folder, and those exceptions are identified before the tree is built.
Shared folders count against storage
A shared folder is added to each member’s account and normally counts towards their quota, and it syncs to their computer as a real folder. Sharing the whole client tree with every person can fill both. Shares are sized to teams, and the allowance needed per user is worked out from the document volumes.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Sync.com on this route, which makes it repeatable: a load can be run again until it is right.
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 Sync.com. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into Sync.com 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.
Cutover
There is no financial cutover on this route. After a short freeze on changes in Partner for Windows (P4W), a final pass over a weekend picks up what changed since the trial. 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 Sync.com. 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
Sync.com is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.
A Sync set-up comes down to accounts and shares. A team plan gives an administrator control over users, two-factor authentication and password resets, which matters more than usual in a service the provider says it cannot see into. The shared folders are then created to match the firm’s teams and its restricted matters.
What is agreed and set up
- Administrator account and a user for each staff member
- Two-factor authentication enforced across the firm
- Team shared folders with view or edit permission per person
- Which matters live in Files and which in Vault
- Rules for client links: passwords, expiry dates, upload rights
- Desktop app installed, with a filing guide for new matters
Questions
Partner for Windows (P4W) to Sync.com: 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 Sync.com?
No. Sync.com does not keep trust ledgers. Trust records from Partner for Windows (P4W) are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.
What happens to records Sync.com has no place for?
On this route that is matters, tasks, time entries, billing records, trust ledgers and 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 Sync.com?
Emails 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 decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from Partner for Windows (P4W) and into Sync.com
Other destinations from Partner for Windows (P4W)
Other systems that move into Sync.com
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 Sync.com are the names and marks of their owners, used here only to identify the two systems.
Moving from Partner for Windows (P4W) to Sync.com?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.