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

Data migration route

Neos to LexWorkplace migration

Neos is a cloud case management system for personal injury work, and LexWorkplace 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.

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

What moves

What moves from Neos to LexWorkplace

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

Records in Neos and their place in LexWorkplace
RecordIn NeosIn LexWorkplaceWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases laid out in tabs, with a Management tab for fee and referral details.Has a place in partName, custom ID, client, type, location, staff, tags and dates. No parties or financial fields.Carried with mapping
ContactsClients, other parties and referrersHeldParties, providers, counsel, case contacts and related contacts.No placeOnly a client name, status, attorneys and tags.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeldCase Docs tab with sub-tabs, viewable as a list or as folders.Has a placeFiled to a matter or to Firm Documents, in folders.Carried across
EmailsEmails saved to matters or to the storeHeldEmails can be tagged to the case file. Outlook is integrated.Has a placeOn the matter’s Email tab, in their own folders.Carried across
NotesFile notes, matter notes and contact notesHeldCase notes, including Special Notes.Has a placeAs Matter Notes on the matter’s Notes tab.Carried across
CalendarAppointments, court dates and deadlinesHeldCase calendars, with statute and deadline alerts.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldChecklists and case tasks, which feed staff dashboards.To be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTimers on a case, which can create value items.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldInvoices in PDF, Word or LEDES format. Payments through LawPay.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeld in partTrust requests can be raised and paid through LawPay.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldUser-defined fields can be added to case tabs.Has a place in partOld categories can become document types, statuses or tags.Carried with mapping
TemplatesPrecedents, document templates and automationHeldA document generation wizard merges templates for one case or many.Has a place in partStored as files in Firm Documents.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntakes tab and intake forms.No placeKept as a readable archive

What the plans mean

Carried across
LexWorkplace has a place for this kind of record. It is loaded there and checked against Neos.
Carried with mapping
LexWorkplace 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
LexWorkplace has no place for it. It is exported in a format that opens without Neos 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. LexWorkplace 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 Neos 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 LexWorkplace cannot hold goes to whatever replaces Neos for matters and billing, or into an archive.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Neos 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 Neos is kept running until the checks on LexWorkplace are finished.

Where the data is now

A firm leaving Neos is leaving a cloud system whose data sits in a database dedicated to that firm. The structure runs tab by tab, and each tab is in effect a table. Many Neos firms came from Needles or Trialworks, so the data often carries conventions two systems old, and the analysis has to read those as well.

  1. A database per firm

    Assembly holds each firm’s records in a separate Azure SQL database. For a migration that means the data set is self-contained, with nothing shared with other customers. How a copy is obtained is arranged with the firm at the start, and the copy and the document files are taken at the same point in time.

  2. Value items hold the money

    Bills, costs, time and settlement entries are value items on the Value tab, with transactions beneath them for payments. A general system splits those across disbursements, time, invoices and receipts. Each value code is mapped to one of them, and the case totals are compared before and after.

  3. Fields inherited from Trialworks

    When a Trialworks firm is converted to Neos, some standard fields land in user-defined fields and in document sub-tabs named after the old tabs. A firm that has been through that carries two layers of structure. Both are read, so a field that looks custom is recognised as the old system’s standard field.

  4. Checklists and calendars

    Work in progress is split between checklist items and case calendar entries, and dashboards are built from both. Open checklist items become tasks in the destination. Calendar entries become events. The two are counted separately in the trial load, because losing either leaves a fee earner with an empty list on the first morning.

More about moving off Neos

Where it is going

LexWorkplace expects every document and email to belong to a matter, so loading it starts with the matter list: name, custom ID, client, type and dates. Uptime Legal states that it runs migration and onboarding for its customers itself. The preparation is getting the old system’s content into a clean client and matter structure, with the exceptions resolved, ready for that load.

  1. Matters carry little, by design

    A matter record holds a name, a custom ID, a client, a type, a location, assigned staff, tags and open and close dates. Parties, court details and financial data have no fields. Those stay in the practice management system, and the two are tied together by using the same matter number as the custom ID.

  2. Clients are only containers

    LexWorkplace says plainly that its clients are for grouping matters, not for client management. A client has a name, a status, primary attorneys and tags. Addresses, phone numbers and contact history from the old system are not loaded here. They go to the practice management system or stay behind.

  3. Three tabs per matter

    Content arrives as documents, emails or notes, each on its own tab with its own folders. Emails held as message files in an old folder tree have to be recognised and loaded as emails, not as documents, or they will not appear where lawyers look for correspondence.

  4. Closed matters and archive

    A matter is closed by giving it a close date, and closed matters can be moved to archive storage, where they keep their place but are not searched or indexed until un-archived. Old matters can therefore be loaded and archived straight away. The firm sets the cut-off year.

  5. Profiling is optional unless enforced

    Document type, status and tags are not required by default, though a firm can switch on mandatory profiling for matters. If the old system had document types, they are mapped to LexWorkplace types during the load. If it had none, the firm chooses between loading unprofiled and assigning types by folder name.

More about moving into LexWorkplace

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in LexWorkplace on this route, which makes it repeatable: a load can be run again until it is right. The maker of LexWorkplace 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 Neos and checking each trial against Neos.

  1. Analysis

    We read what Neos holds and how it is organised, then agree with you where each kind of record will sit in LexWorkplace. 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 LexWorkplace and checked against Neos: 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 Neos, a final pass over a weekend picks up what changed since the trial. Neos 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 Neos 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 fromNeos
Moving toLexWorkplace

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

    What is in it, how its records link, and where each piece would sit in LexWorkplace. 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 LexWorkplace

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

Setting LexWorkplace up for a firm is a short list of decisions made in its settings, plus software on each computer. The decisions are what the firm calls its matter types, document types and statuses, who can open which matters by default, and whether versioning is automatic or manual. The Launcher and the Outlook add-in are then installed for every user.

Set-up decisions in LexWorkplace

  • Matter types, document types, statuses and tag conventions
  • Groups, rights and default permissions for new matters
  • Automatic or manual versioning, and whether profiling is mandatory
  • Linking matters to Clio Manage where the firm uses it
  • Launcher, Office and Outlook add-ins on each Windows or Mac computer
  • A Firm Documents structure for templates, policies and internal files

Questions

Neos to LexWorkplace: what firms ask

We have seen NEOS Web and NEOS DB listed. Are they different from Neos?

Assembly’s own site describes a single product, Neos, used in a browser, with each firm’s records in a dedicated Azure SQL database. Some software lists show NEOS Web and NEOS DB as separate entries. Which system a firm actually holds, and where its data sits, is identified at the start of the analysis.

We are on Needles. Is Neos just an upgrade?

No, it is a migration. Needles keeps its data in a SAP ASE database on the firm’s server and Neos uses Azure SQL in the cloud, so records and documents are converted, not upgraded in place. Assembly says the case logic is the same, which shortens the mapping compared with a move elsewhere.

Can Neos replace our accounting system?

Not the general ledger. Neos records case money as value items, raises invoices and trust requests, and takes payments through LawPay, and it links to QuickBooks Desktop or Online for the books. A firm moving from a system with built-in accounting plans a QuickBooks set-up as part of the same project.

Do trust balances in Neos have a place in LexWorkplace?

No. LexWorkplace does not keep trust ledgers. Trust records from Neos 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 LexWorkplace has no place for?

On this route that is contacts, calendar entries, time entries, billing records, trust ledgers and intake records. They are exported from Neos 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 Neos data is loaded into LexWorkplace?

Matters, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Tasks 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

Neos and LexWorkplace are the names and marks of their owners, used here only to identify the two systems.

Moving from Neos to LexWorkplace?

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

We reply within one business day.