Data migration route
Smokeball to Sync.com migration
Smokeball is a practice management system that runs on the desktop and keeps its data in its maker’s cloud, 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.
SmokeballDesktop and cloud- Documents: Carried across
- Emails: Carried with mapping
- Notes: Carried with mapping
- Templates: Carried with mapping
Sync.comCloud- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: 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
- Custom fields: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 3 mapped
- 9 archived
What moves
What moves from Smokeball to Sync.com
Each row is a kind of record Smokeball holds, whether Sync.com has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping and nine kinds have no place in Sync.com and are archived.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldEach has a matter type for an area of law and a jurisdiction; the number is the Internal Reference. | No placeA matter is a folder in Files or Vault. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldContacts hold roles on matters. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldFiles and folders inside each matter, with version history and full-text search. | 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 | HeldSaved to the matter from Outlook, with attachments linked to the email. | 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 | HeldFile notes are called memos. | Has a place in partOnly as a document written out to the matter’s folder. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | HeldEvents linked to matters, synced with Outlook. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | HeldTasks and workflows. | No place | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | HeldEntered by hand or captured automatically by AutoTime. | 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 | HeldTrust accounts with reconciliation and protected funds. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | Held in partFields come from each matter type’s layouts; firm-added fields are confirmed in the analysis. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | HeldA precedent library of forms and templates that fill from the matter. | Has a place in partPrecedents load as ordinary files. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLeads, and intake forms made in a form builder. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- Sync.com has a place for this kind of record. It is loaded there and checked against Smokeball.
- 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.
- Kept as a readable archive
- Sync.com has no place for it. It is exported in a format that opens without Smokeball 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 Smokeball 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 Smokeball.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Smokeball depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Smokeball is kept running until the checks on Sync.com are finished.
Where the data is now
Leaving Smokeball
Smokeball keeps its data in its own cloud, so a move off it starts with getting a full copy out: matter and contact lists, the files in every matter, and the billing and trust reports. Its reports export contacts and matters to CSV. The detail that takes the time is the matter-type fields, which differ from one kind of matter to the next.
Fields belong to the matter type
Matter details are held in layouts, such as Case Details or Property Details, and the set of layouts depends on the matter type. A family matter and a conveyance have different fields. The extract has to be taken type by type, and each layout mapped to custom fields or a note in the new system.
Internal Reference is the number
What other systems call a matter number, Smokeball calls the Internal Reference. It can be typed by hand or generated from parts, with a counter that some firms reset each calendar year, and individual matters can be overridden. We test the references for duplicates and gaps before using them as the key that documents are matched on.
Memos, and emails with attachments
File notes are memos. Emails saved from Outlook sit in the matter with their attachments, and each attachment keeps a link back to the email it arrived on. Most destinations store the email and the attachment as two unrelated files. Both come across, but that link is generally lost unless the attachment stays inside the email file.
Version history stays behind
Smokeball keeps earlier versions of a file and lets users compare and restore them. A bulk copy of the documents takes the current version of each. If earlier versions of particular documents matter, for instance negotiated contracts, the firm names those matters and the versions are pulled out for them as separate files.
No ledger to move
There is no general ledger in Smokeball. Billing and trust are inside it, and transactions are passed to a linked accounting package: MYOB or Xero in Australia, QuickBooks Online in the US. So the firm’s books stay where they are. What changes is the feed into them: the new system has to be connected to the same accounts from an agreed date.
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 Smokeball 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 Smokeball: 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 Smokeball, a final pass over a weekend picks up what changed since the trial. Smokeball 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 Smokeball 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 Smokeball 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
Smokeball to Sync.com: what firms ask
Can we take our Smokeball matter numbers with us?
Yes in most cases. The Internal Reference is exported with each matter and loaded as the matter number wherever the destination accepts one. If the counter was reset each year, the reference needs its year component to stay unique. We check that before the trial load and report any references used twice.
Do closed matters need to move?
They do not have to. Closed matters can move as full records, as documents only, or stay in the archived copy. The choice turns on how often the firm reopens old files and on its retention obligations. Archive details recorded when a matter was closed are captured in the analysis so they are not lost.
Our office accounts are in a separate accounting package. Does anything happen to them?
The ledger stays in that package. Smokeball has been sending it invoices and payments, and that feed stops at cutover. The new system is connected to the same file from an agreed date, with the account mapping checked on a trial so double posting shows up before go-live. Which system produced each entry is then clear from its date.
Do trust balances in Smokeball have a place in Sync.com?
No. Sync.com does not keep trust ledgers. Trust records from Smokeball 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, contacts, calendar entries, tasks, time entries, billing records, trust ledgers, custom fields and intake records. They are exported from Smokeball 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 Smokeball data is loaded into Sync.com?
Emails, notes and templates are carried with mapping, so each mapping is agreed with you first. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from Smokeball and into Sync.com
Other destinations from Smokeball
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.
Smokeball and Sync.com are the names and marks of their owners, used here only to identify the two systems.
Moving from Smokeball 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.