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

Data migration route

Amazon S3 data to Full data export

Amazon S3 is cloud file storage, and Full data export is a store of data kept as files the firm holds. What lands in Full data export is the register: every file’s name, place, dates and details, with the files themselves stored beside it.

FromAmazon S3Cloud
  1. Documents: Exported in full
  2. Emails: Exported with mapping
  3. Custom fields: Exported with mapping
ToFull data exportFiles
  • 1 carried
  • 2 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Amazon S3 to Full data export

Each row is a kind of record Amazon S3 holds, whether Full data export 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 Full data export
RecordIn Amazon S3In Full data exportWhat 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 placeFiles under their original names, in client and matter folders.Exported in full
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 partFiled emails as message files in the matter’s folder, if the source exposes them.Exported 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 placeExtra columns under their original field names.Exported with mapping

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

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 files, and a register of what each one is.

A database is a poor place to keep documents and a good place to keep facts about them. On this route the files from Amazon S3 are exported to storage the firm controls, and Full data export receives the register: one row per file, with its path, size, dates, author and whatever profile or folder details existed. That register is what makes a large export searchable. It also proves completeness, since the row count and total size can be agreed to the source.

How useful the register is depends on how much Amazon S3 knows about each file. A document management system has a profile to carry. A plain folder has only a path and dates, and the client or matter has to be read out of folder names. Where versions or an audit history exist, each becomes a table of its own. The export is checked by picking documents at random in the source, finding them through Full data export, and opening the file to confirm it is the same one.

Amazon S3 is hosted by its maker and Full data export sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Amazon S3 will release depends on its export tools, and that is confirmed in the analysis.

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

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 Amazon S3 holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything Amazon S3 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 Amazon S3: record counts, totals where Amazon S3 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 Amazon S3, the export is run a final time and checked again. There is nothing to go live. Amazon S3 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 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 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 Amazon S3 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

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

Does the copy in Full data export hold documents from Amazon S3?

Yes. Files under their original names, in client and matter folders. Documents are written out with the rest, and counts and totals are agreed to the reports in Amazon S3 as at the export date.

Does everything in Amazon S3 have a place in Full data export?

On paper, yes: each kind of record Amazon S3 holds has a place in Full data export. 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 is written out to Full data export?

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

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

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