Data migration route
Amazon S3 to QuickBooks Online migration
Amazon S3 is cloud file storage, and QuickBooks Online is a cloud accounting and billing system. Only names and any financial records have a place in a set of books, so little of this moves.
Amazon S3Cloud- Documents: Carried with mapping
- Custom fields: Carried with mapping
QuickBooks OnlineCloud- Emails: Kept as a readable archive
- 2 mapped
- 1 archived
What moves
What moves from Amazon S3 to QuickBooks Online
Each row is a kind of record Amazon S3 holds, whether QuickBooks Online has a place for it, and what is planned. On this route two kinds need mapping and one kind has no place in QuickBooks Online and is archived.
| 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 place in partAttachments on transactions and customers; there are no matter folders. | Carried with mapping |
| 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. | No place | Kept as a readable archive |
| 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 place in partUp to 12 enhanced custom fields per form or profile type, in the Advanced plan. | Carried with mapping |
What the plans mean
- Carried with mapping
- QuickBooks Online 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
- QuickBooks Online 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
Little of this belongs in the accounts.
QuickBooks Online is an accounting package. It takes customers, suppliers, invoices and ledger entries, and has no place for documents, case notes, calendars or leads. From Amazon S3, that usually leaves the contact list, loaded as customers, and any financial records it happens to keep. The table above shows which. This is a small job, and it is better to say so plainly before a firm plans around it.
Loading customers into an accounting system has consequences a contact list elsewhere does not. Every customer can be invoiced, so duplicates and half-complete records turn into billing mistakes. The list is cleaned and matched against the customers already in QuickBooks Online before anything is added. The rest of what Amazon S3 holds is exported in open formats and kept as an archive, or moved on a different route to a system built for it.
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 QuickBooks Online 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 QuickBooks Online
QuickBooks Online is a ledger. Loading a law firm into it means deciding what the firm’s clients, matters, invoices and client money become in a system that has customers, projects and accounts. Records with a financial meaning find a place. Documents, emails, court dates and matter notes do not, and those stay in a practice system or document store beside it.
No matters, so choose a stand-in
A client becomes a customer. A matter becomes a sub-customer, or a project on the Plus and Advanced plans. Sub-customers can nest four levels deep. The choice affects every invoice and report afterwards, so it is made once, before loading, and applied to open and closed matters alike.
Lists load before transactions
Intuit’s import expects the chart of accounts first, then customers, vendors, employees, classes, locations, and products and services. Only then do invoices, bills, journal entries and time activities go in. Intuit says a spreadsheet must have fewer than 1,000 rows, so a firm’s history is loaded in batches and counted batch by batch.
Client money through the accounts
Client money follows the method Intuit documents, through the chart of accounts. A trust bank account and a liability account are created, and each client’s opening balance is posted against their customer record. Its Australian page also advertises trust records, and what they cover is confirmed in the analysis. Whether that meets the trust rules applying to the firm is for its accountant or regulator to say, before loading.
Old invoices or opening balances
Invoices can be imported, and each needs a customer and a product or service that already exists. Loading years of paid invoices also posts income into past periods. One approach is to bring unpaid invoices across as invoices and everything older as opening balances by journal, with the old system kept for the detail. The firm’s accountant chooses.
What has no home
Parties other than the client, matter descriptions, court dates, file notes and documents have no record type here. A file can be attached to a transaction or a customer, which suits a copy of a bill, not a matter file. The analysis lists each of these with where it will live instead.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in QuickBooks Online 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 QuickBooks Online. 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 QuickBooks Online 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 QuickBooks Online. 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 QuickBooks Online
Loaded data is not yet a working system. This is what NewLaw sets up in QuickBooks Online, beyond the migration, so that people can work in it from the first day.
Setting QuickBooks Online up for a law firm is mostly accounting design. The chart of accounts, the way clients and matters appear as customers, the products and services behind each invoice line and the handling of client money are all decided before the first transaction is posted. If a practice system will feed it, that connection and its account mapping are part of the same work.
Set-up decisions in QuickBooks Online
- Chart of accounts, including trust bank and trust liability accounts
- Convention for clients and matters as customers, sub-customers or projects
- Products and services for fees, disbursements and retainers, mapped to accounts
- User roles and what each person can see or post
- Connection to the firm’s practice management or time recording system
- Invoice layout, numbering, tax codes and payment terms
Questions
Amazon S3 to QuickBooks Online: 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 QuickBooks Online?
In part. Attachments on transactions and customers; there are no matter folders. The structure in Amazon S3 is mapped to what QuickBooks Online offers and you see the mapping before the load. File dates are carried.
What happens to records QuickBooks Online has no place for?
On this route that is emails. 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 QuickBooks Online?
Documents 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 QuickBooks Online
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 QuickBooks Online are the names and marks of their owners, used here only to identify the two systems.
Moving from Amazon S3 to QuickBooks Online?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.