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

Data migration route

Keyhouse to NetDocuments migration

Keyhouse is a server-based practice management system, and NetDocuments is a cloud document management system. Documents and email move, filed under the matters they came from. Time, billing and trust have no place in a document system.

FromKeyhouseServer
  1. Documents: Carried across
  2. Emails: Carried across
  3. Matters: Carried with mapping
  4. Templates: Carried with mapping
  5. Contacts: Confirmed in the analysis
  6. Notes: Confirmed in the analysis
  7. Tasks: Confirmed in the analysis
  8. Firm accounts: Confirmed in the analysis
  9. Custom fields: Confirmed in the analysis
  10. Intake: Confirmed in the analysis
ToNetDocumentsCloud
  1. Calendar: Kept as a readable archive
  2. Time and expenses: Kept as a readable archive
  3. Billing: Kept as a readable archive
  4. Trust money: Kept as a readable archive
Readable archiveNo place in NetDocuments
  • 2 carried
  • 2 mapped
  • 6 to confirm
  • 4 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Keyhouse to NetDocuments

Each row is a kind of record Keyhouse holds, whether NetDocuments has a place for it, and what is planned. On this route two kinds of record carry across, two kinds need mapping, four kinds have no place in NetDocuments and are archived and six kinds are confirmed in the analysis.

Records in Keyhouse and their place in NetDocuments
RecordIn KeyhouseIn NetDocumentsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldOrganised as cases.Has a place in partAs a client and matter value with its workspace. Other matter details stay in practice management.Carried with mapping
ContactsClients, other parties and referrersTo be confirmedNo placeConfirmed in the analysis
DocumentsFiles stored in or linked from the systemHeldEmails and documents are stored in the case file.Has a placeImported with profile values, folder, dates and access set per document.Carried across
EmailsEmails saved to matters or to the storeHeldEmails are assigned to cases.Has a placeLoaded as email items profiled to the matter.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedNo placeFile notes are loaded as documents in the matter workspace.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partDates are managed against cases.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTasks are diarised from the case.To be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldKeyhouse Time Recording.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldBills are supported by recorded time.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldKeyhouse Legal Accounts follows the solicitors’ accounts rules.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeAs custom profile attributes, created in the repository before the load.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldDocument generation from the case, and a Brief Builder for court briefs.Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

Carried across
NetDocuments has a place for this kind of record. It is loaded there and checked against Keyhouse.
Carried with mapping
NetDocuments 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.
Kept as a readable archive
NetDocuments has no place for it. It is exported in a format that opens without Keyhouse and handed to the firm as a read-only archive.

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 documents move. The accounts do not.

Moving from a matter system into a document management system is a documents job. NetDocuments has no place for time, invoices or trust, so there is no financial cutover on this route. What it does want is structure. Every document from Keyhouse is filed into a workspace or folder for its client and matter, with a profile that says what it is. The client and matter list becomes that structure, which is why it is cleaned before any file is copied.

A document’s own details count for more here than anywhere. Created and modified dates, author, document type and version become searchable profile fields, and a wrong date on a few thousand files is hard to undo. Email filed to matters is carried as messages. Document copies can be run again, so the trial is repeated until counts and dates agree. Matter data that NetDocuments cannot hold goes to whatever replaces Keyhouse for matters and billing, or into an archive.

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

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

Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.

  1. Lookup tables before documents

    Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.

  2. Workspaces come from the profile

    A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.

  3. Import files are unforgiving

    The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.

  4. Folder limits and depth

    A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.

  5. Security at the right level

    Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.

More about moving into NetDocuments

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in NetDocuments on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Keyhouse holds and how it is organised, then agree with you where each kind of record will sit in NetDocuments. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into NetDocuments and checked against Keyhouse: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in Keyhouse, a final pass over a weekend picks up what changed since the trial. 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

Step 1 of 5: Start with the route

Moving fromKeyhouse
Moving toNetDocuments

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

Setting up NetDocuments

Loaded data is not yet a working system. This is what NewLaw sets up in NetDocuments, beyond the migration, so that people can work in it from the first day.

Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.

Set-up decisions in NetDocuments

  • Cabinet design: one for the firm, or several by purpose
  • Profile attributes, lookup tables and the client and matter hierarchy
  • Workspace layout with default folders, filters and saved searches
  • User groups, cabinet membership and security for restricted matters
  • A feed of new clients and matters from practice management
  • ndOffice, ndMail and Outlook filing on every desk, with training

Questions

Keyhouse to NetDocuments: 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 NetDocuments?

No. NetDocuments does not keep trust ledgers. Trust records from Keyhouse are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.

What happens to records NetDocuments has no place for?

On this route that is calendar entries, time entries, billing records and trust ledgers. They are exported from Keyhouse in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

What has to be decided before Keyhouse data is loaded into NetDocuments?

Matters and templates are carried with mapping, so each mapping is agreed with you first. Contacts, notes, tasks, the firm’s accounts, custom fields and intake records are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

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 NetDocuments are the names and marks of their owners, used here only to identify the two systems.

Moving from Keyhouse to NetDocuments?

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

We reply within one business day.