Data migration route
Bill4Time to SimpleLaw migration
Bill4Time is a cloud accounting and billing system, and SimpleLaw is a cloud practice management system. The financial records lead: balances and open items move, and the matters in SimpleLaw are built around them.
Bill4TimeCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Intake: Confirmed in the analysis
SimpleLawCloud- 7 carried
- 3 mapped
- 3 to confirm
What moves
What moves from Bill4Time to SimpleLaw
Each row is a kind of record Bill4Time holds, whether SimpleLaw has a place for it, and what is planned. On this route seven kinds of record carry across, three kinds need mapping 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. | Has a place | Carried across |
| ContactsClients, other parties and referrers | HeldClients, with the contacts recorded under each. | Has a placeAs leads, clients or other contacts in the CRM. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldFiles stored against contacts and matters; Box and NetDocuments can be connected. | Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | Held in partScheduled items sync with Google Calendar or Outlook Calendar. | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime and expenses with custom rates, expense categories and billing codes. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | HeldBatch invoicing, LEDES, payment plans and write-offs. | Has a place in partInvoices are created in the product; loading invoice history is confirmed in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | HeldOperating and trust funds are kept apart on invoices and reports. | Has a place in partTrust balances are supported; history depth is confirmed in the analysis. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a place | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | Held in partInvoice templates; document templates were not confirmed. | Has a place in partTemplates are rebuilt using SimpleLaw’s own automation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeLeads and intake forms. | Confirmed in the analysis |
What the plans mean
- Carried across
- SimpleLaw has a place for this kind of record. It is loaded there and checked against Bill4Time.
- Carried with mapping
- SimpleLaw 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
Time, bills and balances move. How much history is a decision.
Coming from an accounting or billing system, the records that count are balances: unbilled time, unpaid invoices, client funds, the ledger. A practice management system takes these as opening positions on a matter. So every client and job in Bill4Time needs a matter to land on, and the first piece of work is building that matter list, often from client and project codes that were never meant to be matter numbers.
How much history to bring is the main choice. Paid invoices from years ago can be loaded as records, kept as PDF copies on the matter, or left in a read-only copy of Bill4Time. Most firms bring open items and a period of history, and keep the rest as reports. Opening balances in SimpleLaw are agreed to the trial balance and aged debtors from Bill4Time as at the cutover date, and that load is rehearsed before it is done for real.
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 SimpleLaw 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 SimpleLaw
Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.
Lead, client or contact
A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.
Billing type on each matter
Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.
Storage chosen before loading
If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.
Custom fields named for templates
Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.
Portal access client by client
The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.
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 Bill4Time holds and how its records link, then agree with you, field by field, where each piece will sit in SimpleLaw. 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 Bill4Time, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into SimpleLaw as a trial and checked against Bill4Time: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Bill4Time are frozen for an agreed window, the data is collected a final time and SimpleLaw 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. 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 SimpleLaw. 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 SimpleLaw
Loaded data is not yet a working system. This is what NewLaw sets up in SimpleLaw, beyond the migration, so that people can work in it from the first day.
The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.
Set-up decisions in SimpleLaw
- Labels for documents, activities, expenses and contact IDs
- Custom fields and intake forms for each practice area
- Document templates and the attorney-client agreement
- Workflows for case types that follow a standard process
- User permission sets and client portal visibility
- QuickBooks connection and the online payment processor
Questions
Bill4Time to SimpleLaw: 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 SimpleLaw?
In part. Trust balances are supported; history depth is confirmed in the analysis. The analysis sets out which trust records have a place in SimpleLaw and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.
Does everything in Bill4Time have a place in SimpleLaw?
Most of it does on paper. Emails, 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 SimpleLaw is kept as a readable archive, and you see which before the move.
What has to be decided before Bill4Time data is loaded into SimpleLaw?
Billing records, trust ledgers 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 sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from Bill4Time and into SimpleLaw
Other destinations from Bill4Time
Other systems that move into SimpleLaw
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 SimpleLaw are the names and marks of their owners, used here only to identify the two systems.
Moving from Bill4Time to SimpleLaw?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.