Data migration route
Bill4Time to Litify migration
Bill4Time is a cloud accounting and billing system, and Litify is a cloud case management system. Only part of what Bill4Time holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.
Bill4TimeCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Billing: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Intake: Confirmed in the analysis
LitifyCloud- 6 carried
- 2 mapped
- 5 to confirm
What moves
What moves from Bill4Time to Litify
Each row is a kind of record Bill4Time holds, whether Litify has a place for it, and what is planned. On this route six kinds of record carry across, two kinds need mapping and five 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 placeMatters, by case type. | Carried across |
| ContactsClients, other parties and referrers | HeldClients, with the contacts recorded under each. | Has a placeLoaded as parties and connected by roles. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldFiles stored against contacts and matters; Box and NetDocuments can be connected. | Has a placeLoaded to the document component and attached to matters. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partScheduled items sync with Google Calendar or Outlook Calendar. | Has a placeCalendar events on the matter. | 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 placeTime entries on the matter. | Carried across |
| BillingInvoices, payments and debtor balances | HeldBatch invoicing, LEDES, payment plans and write-offs. | Has a place in partBilling is part of the product. Loading past invoices is scoped 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. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeCustom fields are created before loading. | 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 in Litify’s document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeLoaded as intakes. | Confirmed in the analysis |
What the plans mean
- Carried across
- Litify has a place for this kind of record. It is loaded there and checked against Bill4Time.
- Carried with mapping
- Litify 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
Clients and jobs move. The books stay books.
An accounting or billing system and a case management system overlap less than firms expect. Bill4Time knows clients, jobs, time and invoices. Litify knows cases, parties, documents and deadlines. The client list moves well, and jobs can seed the case list. Time and invoice history has a place only where the case system has a billing side, and the table above shows whether this one does. A general ledger does not belong in a case system.
So the plan has two halves. Records with a place in Litify are loaded and checked there. The rest is exported from Bill4Time as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If Bill4Time is staying as the accounting system, nothing financial needs to move at all, and the job is to line up client and case numbers so the two can be reconciled.
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 Litify 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 Litify
Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.
The design comes first
Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.
One party, many roles
Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.
Open enquiries load as intakes
Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.
Documents load after records
Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.
Validation rules reject bad rows
A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Litify says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Bill4Time and checking each trial against Bill4Time.
Analysis
We read what Bill4Time holds and how its records link, then agree with you, field by field, where each piece will sit in Litify. 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 Litify as a trial and checked against Bill4Time: record counts, financial 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 Litify goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in Bill4Time as at the cutover date. 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 Litify. 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 Litify
Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.
A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.
Set-up decisions in Litify
- Define intake questionnaires and the rules for conversion
- Set case types, matter stages and page layouts
- Build matter plans that create tasks at each stage
- Design document folders and generation templates per case type
- Configure user roles and sharing for restricted matters
- Decide on timekeeping, billing and accounting integrations
Questions
Bill4Time to Litify: 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 Litify?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Bill4Time before the plan is fixed. If Litify turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
Does everything in Bill4Time have a place in Litify?
Most of it does on paper. Emails, notes, trust ledgers, 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 Litify is kept as a readable archive, and you see which before the move.
What has to be decided before Bill4Time data is loaded into Litify?
Billing records and templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, trust ledgers, 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 Litify
Other destinations from Bill4Time
Other systems that move into Litify
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 Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from Bill4Time to Litify?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.