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

Data migration route

Amazon S3 to Neos migration

Amazon S3 is cloud file storage, and Neos is a cloud case management system for personal injury work. The move is matching each file in Amazon S3 to its case in Neos.

FromAmazon S3Cloud
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Custom fields: Carried with mapping
ToNeosCloud
  • 1 carried
  • 2 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Amazon S3 to Neos

Each row is a kind of record Amazon S3 holds, whether Neos has a place for it, and what is planned. On this route one kind of record carries across and two kinds need mapping.

Records in Amazon S3 and their place in Neos
RecordIn Amazon S3In NeosWhat is planned
DocumentsFiles stored in or linked from the systemHeldObjects in buckets; a folder is only the part of the key before a slash.Has a placeCase Docs tab, organised in sub-tabs.Carried across
EmailsEmails saved to matters or to the storeHeld in partOnly where messages were saved to the bucket as files such as .msg or .eml.Has a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis.Carried with mapping
Custom fieldsFields and record types the firm added itselfHeld in partObjects can carry user-defined metadata and tags as name and value pairs.Has a placeUser-defined fields are created on the relevant tab first.Carried with mapping

What the plans mean

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

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

Every document goes to the case it belongs to.

A case management system expects each document to sit on a case, usually in a category such as correspondence, medical records or court documents. Amazon S3 organises files its own way, by profile or by folder. So the move needs two rules: which case a file belongs to, and which category it goes in. The first comes from client and matter references or folder names. The second comes from a document type or a subfolder, and where neither exists the files arrive uncategorised and are marked as such.

Cases must exist in Neos before documents can be attached to them. If the system is already live, files are matched to its case list and the unmatched ones are reported. If it is new, the case list is created first. Dates, authors and file names are kept. Email comes across as message files. Where several versions of a document exist, the firm chooses between loading the latest and loading them all.

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

Where the data is now

Moving a firm’s files out of S3 starts with finding out who put them there and how they are named. A bucket filled by a person usually mirrors a client and matter folder tree. One filled by an application may hold nothing but numbered objects, with the real file names kept in that application’s database. Those are different jobs, and the analysis says which one this is.

  1. Folders are part of the name

    S3 has no folders. A key such as Clients/Nguyen/2019-0412/Letter.pdf is one long name, and the console draws folders from the slashes. Keys can run to 1,024 bytes, far longer than Windows or SharePoint accept, and may contain characters they reject. Those keys are listed in the analysis and shortened by an agreed rule.

  2. Modified dates are upload dates

    The date S3 records against an object is the date it was written to the bucket. A letter drafted in 2014 and uploaded in 2021 shows as 2021. Unless the original date was kept in object metadata or in an index, it cannot be recovered from S3, and document dates in the new system will reflect that.

  3. Archive classes need a restore

    Objects in the S3 Glacier Flexible Retrieval and Deep Archive storage classes cannot be read straight away. Each has to be restored to a temporary copy first, which takes time and is charged by AWS. Closed-matter archives are often stored this way, so the restore is requested before the trial load, not during it.

  4. Versions exist only if enabled

    Versioning is off unless someone switched it on for the bucket. Where it is on, every overwrite keeps the earlier object in full, and a deleted file sits behind a delete marker and is not removed. The firm decides whether earlier versions and deleted objects move, because a plain copy of the bucket brings only the current ones.

  5. Application buckets need the database

    Where a practice or document system used the bucket as its store, the keys are often identifiers and not file names. The matter, the document title and the author live in that system’s database. Copying the bucket alone produces thousands of unnamed files, so the objects are matched to their records before anything is loaded.

More about moving off Amazon S3

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.

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

  1. Analysis

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

Amazon S3 to Neos: what firms ask

Our IT provider set the bucket up. What do you need from them?

Access to read the bucket, arranged in whatever way the firm and its provider decide, and the region it sits in. They are also asked whether versioning is on, whether any objects are in an archive storage class, and whether a person or an application wrote the files. Moving the files out means reading them, so write access is not part of the request.

Will our client and matter folders look the same in the new system?

In outline, if the keys follow a client and matter pattern. Each part of the key between slashes becomes a folder, or is read as the client, the matter number and the document name where the destination files by matter. Keys that fit no pattern are listed for the firm to place by hand or leave in an unsorted folder.

Can the bucket stay as our archive after the move?

It can. A firm may move its active matters into the new system and leave closed files where they are. What matters then is that someone at the firm, not only the IT provider, holds the AWS account details and knows how to find one closed file by client name. That is worth writing down before the project ends.

Do documents from Amazon S3 keep their folders and dates in Neos?

Neos stores documents. Case Docs tab, organised in sub-tabs. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

Does everything in Amazon S3 have a place in Neos?

On paper, yes: each kind of record Amazon S3 holds has a place in Neos. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

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

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

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

Moving from Amazon S3 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.