Data migration route
Bill4Time to Sync.com migration
Bill4Time is a cloud accounting and billing system, and Sync.com is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.
Bill4TimeCloud- Documents: Carried across
- Notes: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Intake: Confirmed in the analysis
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
- 1 carried
- 2 mapped
- 3 to confirm
- 7 archived
What moves
What moves from Bill4Time to Sync.com
Each row is a kind of record Bill4Time 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, seven kinds have no place in Sync.com and are archived and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldThe level under a client; firms may label it matter, case, project or engagement. | No placeA matter is a folder in Files or Vault. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldClients, with the contacts recorded under each. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldFiles stored against contacts and matters; Box and NetDocuments can be connected. | 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 | To be confirmed | Has a place in partMessage files such as .msg or .eml, filed in the matter’s folder. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held | Has a place in partOnly as a document written out to the matter’s folder. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | Held in partScheduled items sync with Google Calendar or Outlook Calendar. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | Held | No place | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime and expenses with custom rates, expense categories and billing codes. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldBatch invoicing, LEDES, payment plans and write-offs. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | HeldOperating and trust funds are kept apart on invoices and reports. | 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 | Held in partInvoice templates; document templates were not confirmed. | 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 Bill4Time.
- 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 Bill4Time 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
An export the firm can open without the system.
Sync.com holds files, and most of what Bill4Time holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used Bill4Time, by client or by year, with a short index file saying what is where.
Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in Sync.com is limited before the export is copied in.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Bill4Time 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 Bill4Time is kept running until the checks on Sync.com are finished.
Where the data is now
Leaving Bill4Time
Most of what a firm has built up in Bill4Time is financial: years of time entries, invoices, payments and trust movements, coded the way its clients require. A move off it is judged by whether those figures arrive intact and still add up by client and matter. The practice management records around them are usually thinner and take less of the effort.
Billing codes clients expect
Firms that bill insurers or corporate clients set up billing codes and expense categories so that LEDES invoices are accepted. Those code lists are the firm’s own. They are extracted as reference data and matched to the destination’s codes before any time entry is loaded, since an unmatched code can cause an e-billing rejection later.
QuickBooks already has copies
The connector has been sending invoices and payments to QuickBooks, where clients appear as customers. If the new system also posts to that QuickBooks file, it must be told about the existing customers and open invoices. Otherwise the first sync creates a second set. The accountant agrees the mapping before go-live.
Client first, then matter
Everything is filed under a client and then a matter, and firms rename that second level to suit themselves. A consultancy arm may call it a project. The analysis records the label in use and checks whether non-legal projects are mixed in with matters, because they may not belong in a legal system.
Calendars synced with Outlook
Where the Google Calendar or Outlook Calendar connection is switched on, scheduled meetings, tasks and time entries pass between the two. Those appointments already exist in the mail system, which is not changing, so they are not loaded twice. Deadlines kept only as Bill4Time tasks are the items that need to be carried across.
Rates for past and future
Bill4Time lets a firm set its own rates alongside its expense categories and billing codes. When time is loaded into a new system the historic entries keep the rate they were billed at. The rate tables for future work are a separate job, rebuilt in the destination and tested by raising a draft invoice on a known matter.
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 Bill4Time 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 Bill4Time: 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 Bill4Time, a final pass over a weekend picks up what changed since the trial. Bill4Time 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 Bill4Time 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 Bill4Time 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
Bill4Time to Sync.com: what firms ask
Can we bring all our old invoices, or only what is still owed?
That depends on the destination. Some systems load paid invoices as history. Others accept open balances only, with the old invoices saved as PDFs on each matter. In both cases the debtor total in the new system is checked against the Bill4Time aged receivables report on the cutover date.
We keep documents in NetDocuments, connected to Bill4Time. Do they move?
They can stay where they are. NetDocuments holds the files and Bill4Time only links matters to them. If the new practice system also connects to NetDocuments, the links are re-made matter by matter. Files uploaded directly into Bill4Time are a different case and are extracted with the matter.
How are trust balances moved?
As an opening balance for each client and matter, agreed with the trust bank statement on the day. The transaction history behind each balance moves too where the destination accepts it. A full trial load is done beforehand as a dress rehearsal, because a trust cutover cannot be re-run the way a document load can.
Do trust balances in Bill4Time have a place in Sync.com?
No. Sync.com does not keep trust ledgers. Trust records from Bill4Time 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 and trust ledgers. They are exported from Bill4Time 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 Bill4Time data is loaded into Sync.com?
Notes and templates are carried with mapping, so each mapping is agreed with you first. Emails, 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 Bill4Time and into Sync.com
Other destinations from Bill4Time
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.
Bill4Time and Sync.com are the names and marks of their owners, used here only to identify the two systems.
Moving from Bill4Time 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.