Data migration route
eBillity to Litify migration
eBillity is a cloud accounting and billing system, and Litify is a cloud case management system. Only part of what eBillity holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.
eBillityCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Time and expenses: Carried across
- Billing: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
LitifyCloud- 5 carried
- 1 mapped
- 7 to confirm
What moves
What moves from eBillity to Litify
Each row is a kind of record eBillity holds, whether Litify has a place for it, and what is planned. On this route five kinds of record carry across, one kind needs mapping and seven kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldLawBillity tracks time and expenses against clients and matters. | Has a placeMatters, by case type. | Carried across |
| ContactsClients, other parties and referrers | Held in partClients and their billing details. | Has a placeLoaded as parties and connected by roles. | Carried across |
| DocumentsFiles stored in or linked from the system | Held in partReceipt images attached to expense entries and invoices. | 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 | To be confirmed | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partCalendar entries can be converted into time entries. | Has a placeCalendar events on the matter. | Carried across |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a place | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimers, weekly timesheets and expenses, approved before billing. | Has a placeTime entries on the matter. | Carried across |
| BillingInvoices, payments and debtor balances | HeldInvoices, LEDES billing and online payments through LawPay or Stripe. | 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 | Held in partIn LawBillity only: client trust funds managed beside billing. | 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 | To be confirmed | Has a place in partTemplates are rebuilt in Litify’s document generation. | Confirmed in the analysis |
| 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 eBillity.
- 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. eBillity 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 eBillity as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If eBillity 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 eBillity 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 eBillity is kept running until the checks on Litify are finished.
Where the data is now
Leaving eBillity
A LawBillity account holds the firm’s time, expenses, invoices and, where it was used, trust balances, under a list of clients and matters. It does not hold the firm’s books, which are in QuickBooks or another package beside it. A move is mostly about carrying unbilled time and unpaid invoices across correctly and keeping the link to the accounting package intact.
Which eBillity product
The company sells general Time Tracker plans as well as LawBillity, and a firm may be on either. Those general plans track time for payroll, projects and client invoicing. Only LawBillity is described as having matters, UTBMS codes and trust, so the plan decides what records exist to move.
Billing lives apart from books
Invoices and payments are raised in LawBillity and synchronised to QuickBooks. Two systems therefore hold a version of each invoice. Before cutover the two are agreed to each other, so the receivables loaded into the new system match what the accounting package already says the firm is owed.
Receipts on expense entries
Staff can photograph a receipt and attach it to an expense entry, and the image can be attached to the invoice. These are easy to overlook because the product is not thought of as holding documents. They are collected with their expense entries so the evidence for a disbursement is not lost.
Trust in LawBillity
LawBillity manages client trust funds alongside billing. Each client’s trust balance is listed with its history and agreed to the trust bank statement at the cutover date. If the firm also tracked trust in QuickBooks, the two records are compared first and any difference is explained before either is loaded.
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 eBillity and checking each trial against eBillity.
Analysis
We read what eBillity 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 eBillity, 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 eBillity: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in eBillity 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 eBillity as at the cutover date. eBillity 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 eBillity 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 eBillity 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
eBillity to Litify: what firms ask
Does our unbilled time come across?
Time and expense entries that have not been invoiced are read with their date, person, matter, service item, description and rate. They are loaded as unbilled entries where the new system accepts them. A final billing round in LawBillity before cutover means less work in progress has to be carried.
We also use QuickBooks with it. Does that change?
QuickBooks stays where it is unless the firm is replacing it too. What changes is the connection: the new practice system has to post invoices and payments to the same QuickBooks company in place of LawBillity. The switch is timed so no invoice is posted twice or missed.
Can we keep our invoice numbers?
Invoice numbers belong to the invoice record, and where the LawBillity data supplies them they are kept on each historical invoice brought across. The new system’s next number is then set above the highest LawBillity number so the sequence continues, provided the destination allows the starting number to be set. That is checked in the analysis.
Do trust balances in eBillity 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 eBillity 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 eBillity have a place in Litify?
Most of it does on paper. Emails, notes, tasks, trust ledgers, custom fields, templates 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 eBillity data is loaded into Litify?
Billing records are carried with mapping, so each mapping is agreed with you first. Emails, notes, tasks, trust ledgers, custom fields, templates 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 eBillity and into Litify
Other destinations from eBillity
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.
eBillity and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from eBillity 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.