Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

Keyhouse data to Full data export

Keyhouse is a server-based practice management system, and Full data export is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what Keyhouse holds and keeps it readable and open to queries.

FromKeyhouseServer
  1. Matters: Exported in full
  2. Documents: Exported in full
  3. Calendar: Exported in full
  4. Tasks: Exported in full
  5. Time and expenses: Exported in full
  6. Billing: Exported in full
  7. Trust money: Exported in full
  8. Emails: Exported with mapping
  9. Templates: Exported with mapping
  10. Contacts: Confirmed in the analysis
  11. Notes: Confirmed in the analysis
  12. Firm accounts: Confirmed in the analysis
  13. Custom fields: Confirmed in the analysis
  14. Intake: Confirmed in the analysis
ToFull data exportFiles
  • 7 carried
  • 2 mapped
  • 5 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Keyhouse to Full data export

Each row is a kind of record Keyhouse holds, whether Full data export has a place for it, and what is planned. On this route seven kinds of record carry across, two kinds need mapping and five kinds are confirmed in the analysis.

Records in Keyhouse and their place in Full data export
RecordIn KeyhouseIn Full data exportWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldOrganised as cases.Has a placeA matters table keyed by the original matter number.Exported in full
ContactsClients, other parties and referrersTo be confirmedHas a placeA contacts table and a table of each contact’s role on each matter.Confirmed in the analysis
DocumentsFiles stored in or linked from the systemHeldEmails and documents are stored in the case file.Has a placeFiles under their original names, in client and matter folders.Exported in full
EmailsEmails saved to matters or to the storeHeldEmails are assigned to cases.Has a place in partFiled emails as message files in the matter’s folder, if the source exposes them.Exported with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeA notes table with matter, author and date for each note.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partDates are managed against cases.Has a placeA table of appointments and key dates; nothing shows it as a diary.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldTasks are diarised from the case.Has a placeA table of tasks with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldKeyhouse Time Recording.Has a placeA time entries table with fee earner, matter, units, rate and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldBills are supported by recorded time.Has a placeInvoice, line and receipt tables; invoice PDFs can be kept beside them.Exported in full
Trust moneyTrust or client account ledgers and balancesHeldKeyhouse Legal Accounts follows the solicitors’ accounts rules.Has a placeA trust transactions table; ledger reports can be kept as PDF beside it.Exported in full
Firm accountsGeneral ledger, office account and payablesTo be confirmedHas a place in partJournals and account balances, where the source held a general ledger.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeExtra columns under their original field names.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldDocument generation from the case, and a Brief Builder for court briefs.Has a place in partTemplate files only; the merge fields in them will not run.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a place in partAn enquiries table, where the source tracked leads.Confirmed in the analysis

What the plans mean

Exported in full
Full data export has a place for this kind of record. It is loaded there and checked against Keyhouse.
Exported with mapping
Full data export 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

Not a new system. A complete copy the firm can query.

Writing Keyhouse out to Full data export is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Keyhouse as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Keyhouse stays untouched until the copy in Full data export has been checked.

Where the data is now

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving off Keyhouse

Where it is going

A full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.

  1. Tables that still join up

    Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.

  2. Documents with an index

    Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.

  3. Reports a person can read

    Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.

  4. What an export does not keep

    Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.

  5. Checked while the source is open

    Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.

More about moving into Full data export

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what Keyhouse holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything Keyhouse holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to Full data export as a trial and checked against Keyhouse: record counts, totals where Keyhouse holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in Keyhouse, the export is run a final time and checked again. There is nothing to go live. Keyhouse is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

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

Step 1 of 5: Start with the route

Moving fromKeyhouse
Moving toFull data export

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what Keyhouse holds

    What is in it, how its records link, and where each piece would sit in Full data export. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. 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

Structure, permissions and handover

Full data export is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.

What is agreed and set up

  • Folder layout for tables, documents and reports
  • What the key to tables, columns and identifiers records
  • Where the copies are stored and who is custodian
  • Who may open it, as approved by a partner
  • Which look-ups staff must be able to do unaided
  • Retention period and the date it is next reviewed

Questions

Keyhouse to Full data export: 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.

Does the copy in Full data export hold trust ledgers from Keyhouse?

Yes. A trust transactions table; ledger reports can be kept as PDF beside it. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Keyhouse as at the export date.

Does everything in Keyhouse have a place in Full data export?

Most of it does on paper. Contacts, 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 Full data export is kept as a readable archive, and you see which before the move.

What has to be decided before Keyhouse is written out to Full data export?

Emails and templates are exported with mapping, so each mapping is agreed with you first. Contacts, notes, the firm’s accounts, custom fields and intake records are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.

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.

How we do itDiscovery to rollout, step by step

Keyhouse and Full data export are the names and marks of their owners, used here only to identify the two systems.

Moving from Keyhouse to Full data export?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.