Data migration route
Keyhouse to SimpleLaw migration
Keyhouse is a server-based practice management system, and SimpleLaw is a cloud one. Both run a whole practice, so this is a full move, and the financial records set the timetable.
KeyhouseServer- Matters: Carried across
- Documents: 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
- Contacts: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Intake: Confirmed in the analysis
SimpleLawCloud- 5 carried
- 3 mapped
- 6 to confirm
What moves
What moves from Keyhouse to SimpleLaw
Each row is a kind of record Keyhouse holds, whether SimpleLaw has a place for it, and what is planned. On this route five kinds of record carry across, three kinds need mapping and six kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldOrganised as cases. | Has a place | Carried across |
| ContactsClients, other parties and referrers | To be confirmed | Has a placeAs leads, clients or other contacts in the CRM. | Confirmed in the analysis |
| DocumentsFiles stored in or linked from the system | HeldEmails and documents are stored in the case file. | 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 | HeldEmails are assigned to cases. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partDates are managed against cases. | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTasks are diarised from the case. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldKeyhouse Time Recording. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | HeldBills are supported by recorded time. | 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 | HeldKeyhouse Legal Accounts follows the solicitors’ accounts rules. | Has a place in partTrust balances are supported; history depth is confirmed in the analysis. | Carried with mapping |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | No placeGeneral ledger stays in QuickBooks or another accounting package. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a place | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldDocument generation from the case, and a Brief Builder for court briefs. | 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 Keyhouse.
- 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
The whole practice moves, accounts included.
A move between two practice management systems is the widest kind there is. Keyhouse and SimpleLaw each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.
The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with Keyhouse’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.
Keyhouse runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. SimpleLaw is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving Keyhouse
Keyhouse is sold as modules, so the first step is listing which ones the firm has and which it really uses. A firm with Case Management and Legal Accounts is moving cases, documents and client ledgers together. One that also uses dictation, the mobile app or an iManage link has more places where records sit. Hosting matters too: on premise and Keyhouse 365 are collected differently.
Cases, not matters
Keyhouse speaks of cases and case files. Each one gathers its emails, documents, dates and tasks. In a destination that uses matters the mapping is one to one, but the case reference is what documents and ledger entries hang from, so it is carried across unchanged as the matter number or in a reference field.
Briefs built in Keyhouse
The Brief Builder assembles court briefs from documents on the case. A finished brief is a document and moves like any other. The tool does not. Litigation teams that depend on it should see how the new system produces a paginated brief before go-live, using one of their own cases from the trial load.
Dictation in the case file
Digital dictation lets a solicitor dictate straight into a case file for a secretary to check. Those recordings are counted in the analysis. The typed result is the record, so completed recordings can stay in the archive, but any dictation still waiting to be typed at cutover is finished in Keyhouse first.
Documents may be in iManage
Keyhouse integrates with iManage and with ShareFile. Where a firm uses iManage, its documents may be in that system and Keyhouse holds the case and accounts data. The document move is then an iManage question, and the link between each workspace and its case has to survive whatever replaces Keyhouse.
Irish accounts rules
Legal Accounts is built to comply with the solicitors’ accounts rules that Irish firms work under. A destination has to handle client account ledgers under those same rules, in euro. That narrows the field more than any other requirement, so it is checked before the firm spends time comparing features elsewhere.
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 Keyhouse 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 Keyhouse, 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 Keyhouse: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Keyhouse 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. Keyhouse 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 Keyhouse 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 Keyhouse 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
Keyhouse to SimpleLaw: what firms ask
We are on Keyhouse 365. How is our data collected?
Keyhouse 365 is the vendor’s cloud service, so the database and documents are on its platform and a copy is requested through the firm. For an on-premise installation the copy is taken from the firm’s own server. Either way we check the copy against Keyhouse’s reports before the trial load.
Can historical accounts data come with us?
Balances for each client and case are loaded and reconciled to the closing reports. Older postings can be loaded only if the destination accepts historical transactions, and many do not. Where they cannot go in, ledger cards are saved as PDFs to each open case and the full history stays in the archived system.
Do case numbers stay the same?
Yes, where the new system lets a number be supplied. The Keyhouse case reference becomes the matter number, and documents and ledgers are matched on it during the load. If the destination generates its own numbers, the old reference is stored on the matter in a reference field.
Do trust balances in Keyhouse 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 Keyhouse have a place in SimpleLaw?
Most of it does on paper. Contacts, emails, notes, the firm’s accounts, 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 Keyhouse data is loaded into SimpleLaw?
Billing records, trust ledgers and templates are carried with mapping, so each mapping is agreed with you first. Contacts, emails, notes, the firm’s accounts, 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 Keyhouse and into SimpleLaw
Other destinations from Keyhouse
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.
Keyhouse and SimpleLaw are the names and marks of their owners, used here only to identify the two systems.
Moving from Keyhouse 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.