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

Data migration route

Keyhouse to Neos migration

Keyhouse is a server-based practice management system, and Neos is a cloud case management system for personal injury work. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.

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

What moves

What moves from Keyhouse to Neos

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

Records in Keyhouse and their place in Neos
RecordIn KeyhouseIn NeosWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldOrganised as cases.Has a placeCases by case type.Carried across
ContactsClients, other parties and referrersTo be confirmedHas a placeParties, providers and case contacts. Contacts can be imported from CSV.Confirmed in the analysis
DocumentsFiles stored in or linked from the systemHeldEmails and documents are stored in the case file.Has a placeCase Docs tab, organised in sub-tabs.Carried across
EmailsEmails saved to matters or to the storeHeldEmails are assigned to cases.Has a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partDates are managed against cases.Has a placeCase calendar entries.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks are diarised from the case.Has a placeLoaded as checklist items.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldKeyhouse Time Recording.Has a place in partTime can be held as value items. The treatment of old entries is confirmed in the analysis.Carried with mapping
BillingInvoices, payments and debtor balancesHeldBills are supported by recorded time.Has a place in partInvoices exist in Neos. Loading past invoices is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldKeyhouse Legal Accounts follows the solicitors’ accounts rules.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeThe general ledger stays in QuickBooks.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeUser-defined fields are created on the relevant tab first.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldDocument generation from the case, and a Brief Builder for court briefs.Has a place in partTemplates are rebuilt for Neos document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeIntakes tab. Simple intake imports from CSV are supported.Confirmed in the analysis

What the plans mean

Carried across
Neos has a place for this kind of record. It is loaded there and checked against Keyhouse.
Carried with mapping
Neos 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

Matters become cases. The ledgers need a home.

Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Neos. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.

Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from Keyhouse has to be given a case type in Neos, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Neos is exported as reports and ledgers the firm can open without Keyhouse, and kept as the record of what was billed and held.

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

Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.

  1. Every figure needs a value code

    Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.

  2. Lists are set up first

    Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.

  3. Documents go to sub-tabs

    Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.

  4. Reminders split two ways

    Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.

  5. Assembly runs its own conversions

    Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.

More about moving into Neos

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 Neos 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 Keyhouse and checking each trial against Keyhouse.

  1. Analysis

    We read what Keyhouse holds and how its records link, then agree with you, field by field, where each piece will sit in Neos. Anything with no place there comes across as a note or stays behind, and you see which before the move.

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

  3. Trial load

    The data is loaded into Neos as a trial and checked against Keyhouse: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Keyhouse are frozen for an agreed window, the data is collected a final time and Neos 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 Keyhouse as at the cutover date. 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 toNeos

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

Loaded data is not yet a working system. The maker of Neos runs or arranges the set-up of its product, so this is what has to be decided and put in place in Neos, whoever does the work, before people rely on it from the first day.

Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.

Set-up decisions in Neos

  • Set case types, statuses and staff roles
  • Agree the value code list with accounts staff
  • Build checklists for each case type and stage
  • Create user-defined fields for data the tabs lack
  • Prepare document templates for the generation wizard
  • Connect Microsoft 365, QuickBooks and the phone system

Questions

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

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 Keyhouse before the plan is fixed. If Neos 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 Keyhouse have a place in Neos?

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

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

Emails, time entries, billing records and templates are carried with mapping, so each mapping is agreed with you first. Contacts, notes, trust ledgers, 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.

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

Moving from Keyhouse to Neos?

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

We reply within one business day.