Data migration route
Amazon S3 to MyCase migration
Amazon S3 is cloud file storage, and MyCase is a cloud practice management system. The move is about deciding which folder is which matter, then filing every document against it.
Amazon S3Cloud- Documents: Carried across
- Emails: Carried with mapping
- Custom fields: Carried with mapping
MyCaseCloud- 1 carried
- 2 mapped
What moves
What moves from Amazon S3 to MyCase
Each row is a kind of record Amazon S3 holds, whether MyCase has a place for it, and what is planned. On this route one kind of record carries across and two kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldObjects in buckets; a folder is only the part of the key before a slash. | Has a placeFiled in folders under each case. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partOnly where messages were saved to the bucket as files such as .msg or .eml. | Has a place in partSaved emails can be filed to a case; it does not hold mailboxes. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | Held in partObjects can carry user-defined metadata and tags as name and value pairs. | Has a placeFields are created on cases or contacts before records are loaded. | Carried with mapping |
What the plans mean
- Carried across
- MyCase has a place for this kind of record. It is loaded there and checked against Amazon S3.
- Carried with mapping
- MyCase 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
Folders become matters with documents.
Files in Amazon S3 are organised the way the firm’s people organised them: by client, by year, by lawyer, sometimes all three. MyCase wants every document on a matter. The analysis reads the folder tree and proposes a rule, for example that the second folder level is the matter, then lists every folder the rule does not fit. Those exceptions are the real work. A folder called Misc or Old Files has to be given a home by someone who knows the firm.
Folder names carry what a matter record should hold properly: client name, matter description, sometimes a file number. Where the names are consistent, matters and contacts can be created from them. Where they are not, the matter list is built first, in a spreadsheet the firm corrects, and the documents are loaded against it. File dates are preserved, so a document still shows when it was written and not when it was moved.
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 MyCase are finished.
Where the data is now
Leaving Amazon S3
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in MyCase
Loading a firm into MyCase means turning matters into cases and deciding what each case is called, numbered and filed under. The users, practice areas and custom fields have to exist first, because the records point at them. Money needs the most thought: an opening balance can be brought in simply, but how much invoice and trust history is rebuilt behind it is agreed in the analysis.
Every case name is unique
MyCase will not accept two cases with the same name. A firm with forty matters called Estate Planning, or two files for the same pair of litigants, needs a naming pattern before the trial load. Client surname plus the old matter number is one option, and it keeps the old number in view.
Old numbers fit as they are
The case number field takes letters, digits and punctuation, so a number such as 2019-0457/LIT can be kept without reformatting. It is worth keeping it tidy: the email tools match incoming mail to a case by finding the case number in the subject line.
Open or closed, nothing between
A case in MyCase is either open or closed, with a closed date. Source systems often have more states than that: pending, on hold, archived, awaiting payment. Each is mapped to open or closed during the analysis, and the original status can be kept in a custom field.
Practice areas build themselves
On import, MyCase creates a practice area for every distinct value it is given. Family, Family Law and Fam. Law would become three. The source list is reduced to one agreed set during clean-up, so the firm starts with a short list of practice areas it chose.
Lead attorney must exist
The lead attorney on a case has to be a user in the account. Departed fee earners who still own closed matters are a common snag. They are either mapped to a current user, or their name is recorded in a custom field on the case.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in MyCase on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Amazon S3 holds and how it is organised, then agree with you where each kind of record will sit in MyCase. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into MyCase 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.
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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Amazon S3 holds
What is in it, how its records link, and where each piece would sit in MyCase. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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 MyCase
Loaded data is not yet a working system. This is what NewLaw sets up in MyCase, beyond the migration, so that people can work in it from the first day.
A loaded MyCase account is not yet a working one. The firm still has to decide how cases are classified, who can see what, how money is handled and what clients are shown in the portal. Document templates are rebuilt against MyCase’s own merge fields, since precedents written for another system’s field codes will not merge here. Staff are trained on their own cases once the trial load has been checked.
Set-up decisions in MyCase
- Practice areas and custom fields for cases and contacts
- Trust and operating bank accounts with opening balances per case
- Word document templates rebuilt with MyCase merge fields
- Intake forms and lead pipeline for each practice area
- User roles and who can open which cases
- QuickBooks sync or the MyCase Accounting add-on
Questions
Amazon S3 to MyCase: 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 MyCase?
MyCase stores documents. Filed in folders under each case. 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 MyCase?
On paper, yes: each kind of record Amazon S3 holds has a place in MyCase. 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 MyCase?
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.
Other routes
Other routes from Amazon S3 and into MyCase
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Amazon S3 and MyCase are the names and marks of their owners, used here only to identify the two systems.
Moving from Amazon S3 to MyCase?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.