Data migration route
TimeSolv to Litify migration
TimeSolv is a cloud accounting and billing system, and Litify is a cloud case management system. Only part of what TimeSolv holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.
TimeSolvCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Intake: Carried across
- Billing: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
LitifyCloud- 6 carried
- 2 mapped
- 5 to confirm
What moves
What moves from TimeSolv to Litify
Each row is a kind of record TimeSolv 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 | HeldMatters sit under clients. They carry billing settings more than case detail. | Has a placeMatters, by case type. | Carried across |
| ContactsClients, other parties and referrers | HeldClients and their contacts; leads are tracked in the CRM. | Has a placeLoaded as parties and connected by roles. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldNested folders and tags inside TimeSolv, or a linked Dropbox or NetDocuments account. | 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 | HeldNotes on clients and matters. | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeCalendar events on the matter. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | HeldProject management with phases, tasks, estimates and budgets. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldThe core record, entered on the web, on mobile or offline through the TimeSync app. | Has a placeTime entries on the matter. | Carried across |
| BillingInvoices, payments and debtor balances | Held | 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 | HeldTrust balances can be applied to approved invoices. | 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 partDocuments can be generated from client and matter data. | Has a place in partTemplates are rebuilt in Litify’s document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldCRM tracks prospects through intake statuses the firm defines. | Has a placeLoaded as intakes. | Carried across |
What the plans mean
- Carried across
- Litify has a place for this kind of record. It is loaded there and checked against TimeSolv.
- 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. TimeSolv 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 TimeSolv as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If TimeSolv 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 TimeSolv 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 TimeSolv is kept running until the checks on Litify are finished.
Where the data is now
Leaving TimeSolv
When the destination is a full practice management system, leaving TimeSolv is only part of the job. TimeSolv knows who the client is, what was billed and what is owed. It does not know the court, the other side or the next deadline. Its billing records move across, and the rest of each matter has to be gathered from wherever the firm has been keeping it.
A matter is a billing file
A TimeSolv matter holds rates, billing arrangements, budgets and balances. The parties, key dates and file notes that a practice management system expects are often in Outlook, a spreadsheet or the paper file. Part of the analysis is asking where those live, and whether they are loaded with the billing data or entered as matters are next worked on.
Trust here, ledger elsewhere
Client trust balances are kept in TimeSolv, while the bank accounts and general ledger are in QuickBooks, Xero or AccountEdge. The trust listing from TimeSolv and the trust bank balance from the accounting package are agreed with each other before cutover. Only then are opening balances entered in the new system.
Phases, tasks and budgets
Matter plans split a job into phases and tasks with estimated hours and fixed fees, and time is recorded against task codes. Many destinations bill by matter with no phase beneath it. Where budgets matter to clients, the firm decides whether phases become sub-matters, activity codes or a report run from the old data.
Documents in three places
Files may be in TimeSolv’s own folders, in a linked Dropbox account or in NetDocuments workspaces. A single firm can have all three if it changed approach over the years. Each store is listed with its volume, and documents already in NetDocuments or Dropbox can often stay where they are.
Many years of time entries
The product dates from 1999, so a long-standing firm can hold a very long run of billed time in it. Loading all of it into a new system is seldom worth the effort. A common split is open matters with full detail, closed matters as a summary, and the complete history kept in the read-only copy.
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 TimeSolv and checking each trial against TimeSolv.
Analysis
We read what TimeSolv 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 TimeSolv, 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 TimeSolv: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in TimeSolv 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 TimeSolv as at the cutover date. TimeSolv 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 TimeSolv 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 TimeSolv 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
TimeSolv to Litify: what firms ask
We use TimeSolv with QuickBooks. Which one is the source for debtor balances?
TimeSolv, because that is where invoices are raised and payments applied by matter. QuickBooks holds the same totals at firm level once synced. The two are compared in the analysis. A difference usually points to a payment entered on one side only, and it is fixed before the trial load.
Will our unbilled time come across?
Unbilled time and expenses are the records most worth moving, since they are money not yet invoiced. They are loaded against the right matter and timekeeper with their original dates and narratives. Running a final billing cycle in TimeSolv first leaves less work in progress to carry.
We are on the Pro edition, not Legal. Is the move any different?
The records are the same kind: clients, the jobs under them, time, expenses and invoices. Extraction and checking are planned the same way. What changes is the destination, since a system built for law firms will expect matter types and trust rules that a consultancy or accounting practice never needed.
Do trust balances in TimeSolv 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 TimeSolv 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 TimeSolv have a place in Litify?
Most of it does on paper. Emails, notes, calendar entries, trust ledgers and custom fields 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 TimeSolv data is loaded into Litify?
Billing records and templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, calendar entries, trust ledgers and custom fields 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 TimeSolv and into Litify
Other destinations from TimeSolv
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.
TimeSolv and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from TimeSolv 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.