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

Data migration route

Amazon S3 to Sync.com migration

Amazon S3 and Sync.com are both cloud file storage. The folders move as they are, and the work is in permissions, paths and links.

FromAmazon S3Cloud
  1. Documents: Carried across
  2. Emails: Carried with mapping
ToSync.comCloud
  1. Custom fields: Kept as a readable archive
Readable archiveNo place in Sync.com
  • 1 carried
  • 1 mapped
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Amazon S3 to Sync.com

Each row is a kind of record Amazon S3 holds, whether Sync.com has a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping and one kind has no place in Sync.com and is archived.

Records in Amazon S3 and their place in Sync.com
RecordIn Amazon S3In Sync.comWhat 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 and folders within the path limit; some file types are skipped by the apps.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 partMessage files such as .msg or .eml, filed in the matter’s folder.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.No placeKept as a readable archive

What the plans mean

Carried across
Sync.com has a place for this kind of record. It is loaded there and checked against Amazon S3.
Carried with mapping
Sync.com holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
Kept as a readable archive
Sync.com has no place for it. It is exported in a format that opens without Amazon S3 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

Same folders, new home.

Copying folders from Amazon S3 to Sync.com sounds like a drag and drop, and for a few gigabytes it is. For a firm’s whole document store the trouble is in the detail. The two stores have different limits on path length and different rules about characters in file names. Files open on someone’s desk during the copy are skipped. Modified dates are reset unless the copy is made with a tool that preserves them. Each of these is checked on a trial copy first.

Permissions and links do not travel. Who can see which folder is set up again in Sync.com, and it is a good moment to replace access granted to individuals over the years with groups. Shared links sent to clients stop working when the old store is switched off, so the live ones are listed and reissued. Documents that point at other documents by path, common in spreadsheets, are found and reported. The final pass copies only what changed since the trial.

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 Sync.com 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

A firm that moves its files to Sync is usually doing so for confidentiality, and the load has to respect how the service is built to deliver it. Files are encrypted before they leave the computer. Nobody at Sync can look inside the account to confirm what arrived, so the checking is done from the firm’s side, against the list of what was sent.

  1. Files or Vault

    Open matters belong in Files, where they sync to the people working on them. Closed matters can go to Vault, which holds them in the cloud without putting a copy on every laptop. The firm supplies its open and closed matter lists so each folder is sent to the right side.

  2. A 248 character path limit

    Sync sets a maximum path length of 248 characters to stay compatible between Windows and Mac, and its apps skip anything longer. That is tighter than most systems a firm will be coming from. Folder names are shortened in the plan, and Sync’s own guidance favours a tree only a few levels deep.

  3. What the apps leave out

    The desktop apps do not upload shortcut files, temporary Office files or names containing a slash, and they warn against several other characters on Windows. A copy to Vault produces a transfer report listing what was skipped. That report is reconciled against the source file list after every load.

  4. Permissions come from the top folder

    Sharing is set on a folder and flows down to all of its contents. A matter that needs different access from the rest of a client’s work cannot simply sit one level down with tighter settings. It becomes its own shared folder, and those exceptions are identified before the tree is built.

  5. Shared folders count against storage

    A shared folder is added to each member’s account and normally counts towards their quota, and it syncs to their computer as a real folder. Sharing the whole client tree with every person can fill both. Shares are sized to teams, and the allowance needed per user is worked out from the document volumes.

More about moving into Sync.com

How NewLaw runs it

Four steps, in this order.

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

  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 Sync.com. 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 Sync.com 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 toSync.com

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 Sync.com. 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

Sync.com is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

A Sync set-up comes down to accounts and shares. A team plan gives an administrator control over users, two-factor authentication and password resets, which matters more than usual in a service the provider says it cannot see into. The shared folders are then created to match the firm’s teams and its restricted matters.

What is agreed and set up

  • Administrator account and a user for each staff member
  • Two-factor authentication enforced across the firm
  • Team shared folders with view or edit permission per person
  • Which matters live in Files and which in Vault
  • Rules for client links: passwords, expiry dates, upload rights
  • Desktop app installed, with a filing guide for new matters

Questions

Amazon S3 to Sync.com: 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 Sync.com?

Sync.com stores documents. Files and folders within the path limit; some file types are skipped by the apps. 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.

What happens to records Sync.com has no place for?

On this route that is custom fields. They are exported from Amazon S3 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 Amazon S3 data is loaded into Sync.com?

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

Moving from Amazon S3 to Sync.com?

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

We reply within one business day.