Data migration route
Time59 to Litify migration
Time59 is a cloud accounting and billing system, and Litify is a cloud case management system. Only part of what Time59 holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.
Time59Cloud- Matters: Carried across
- Contacts: Carried across
- Time and expenses: Carried across
- Billing: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
LitifyCloud- 3 carried
- 2 mapped
- 3 to confirm
What moves
What moves from Time59 to Litify
Each row is a kind of record Time59 holds, whether Litify has a place for it, and what is planned. On this route three kinds of record carry across, two 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 | Held in partNo matter record as such: a client, optionally split into projects, stands in for one. | Has a placeMatters, by case type. | Carried across |
| ContactsClients, other parties and referrers | Held in partClients only, with billing details and an optional client group code. | Has a placeLoaded as parties and connected by roles. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | To be confirmed | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime and expense records by timekeeper code, with UTBMS codes available. | Has a placeTime entries on the matter. | Carried across |
| BillingInvoices, payments and debtor balances | HeldInvoices, payments, interest profiles, fixed fee projects and LEDES output. | 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 | HeldClient trust balances, with evergreen replenishment settings. | 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 formats and footers only. | Has a place in partTemplates are rebuilt in Litify’s document generation. | Carried with mapping |
What the plans mean
- Carried across
- Litify has a place for this kind of record. It is loaded there and checked against Time59.
- 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. Time59 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 Time59 as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If Time59 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 Time59 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 Time59 is kept running until the checks on Litify are finished.
Where the data is now
Leaving Time59
A Time59 account holds a small, tidy set of records: clients, projects, timekeepers, time, expenses, invoices, payments and trust. There are no documents or calendars to worry about. The thinking goes into structure. Time59 has clients and projects where the next system will have clients and matters, and the two do not line up one to one.
Is each client a matter?
Many firms use the two name lines on a client record for the client and the matter, so that John Smith has one Time59 client for his divorce and another for his will. Others put matters in projects. The firm’s habit is confirmed first, and Time59 clients are then merged into real clients with matters beneath.
One login for everyone
The whole firm signs in with a single shared username, so there are no individual user records to map across. Who did the work is recorded by timekeeper code on each time entry. Each code is matched to a named user in the new system, including the codes of people who have since left the firm.
Beginning balances
Time59 does not import billing data from other software, so a firm that came to it from another system started each client with a beginning balance. That figure has no invoices behind it. Clients still carrying a beginning balance are listed, and the firm decides how the amount is described in the new system.
Projects set the rate
Hourly rates and fixed fees are set through projects under a client, and fixed fee projects can recur up to a limit. In the destination those become rate arrangements or fee schedules on a matter. Recurring fixed fees are identified one by one, since a missed one means a client is not billed next month.
Evergreen trust settings
Each client can have a trust replenishment trigger, a minimum required balance and wording that appears on the invoice. The balances move as opening trust balances. Trigger amounts are settings, and they are re-entered in the new system for the clients who rely on them, checked against the Time59 list.
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 Time59 and checking each trial against Time59.
Analysis
We read what Time59 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 Time59, 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 Time59: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Time59 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 Time59 as at the cutover date. Time59 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 Time59 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 Time59 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
Time59 to Litify: what firms ask
How does data come out of Time59?
The vendor describes a Microsoft Excel export for downloading data from the account. Invoices can also be downloaded as PDFs. Between the two, the clients, time, expenses, invoices and payments can be reassembled. What the export contains for trust transactions is checked in the analysis before a destination is mapped.
Time59 gave us no matter numbers. What do we do about that?
It becomes a decision, not an obstacle. A new system will usually want a number on each matter. Numbers are generated during the trial load in whatever format the firm prefers, and the Time59 client name is kept on the matter so staff can still find things the way they used to.
Our case files are on paper and in Outlook. What moves?
From Time59, only the billing side: who the clients are, what was billed, what is owed and what is held in trust. The rest was never in it. If the firm wants documents and emails in the new system too, those are gathered from folders and mailboxes as a separate piece of work.
Do trust balances in Time59 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 Time59 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 Time59 have a place in Litify?
Most of it does on paper. Notes, 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 Time59 data is loaded into Litify?
Billing records and templates are carried with mapping, so each mapping is agreed with you first. Notes, 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 Time59 and into Litify
Other destinations from Time59
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.
Time59 and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from Time59 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.