Data migration route
Amazon S3 to Soluno migration
Amazon S3 is cloud file storage, and Soluno 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: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
SolunoCloud- 3 to confirm
What moves
What moves from Amazon S3 to Soluno
Each row is a kind of record Amazon S3 holds, whether Soluno has a place for it, and what is planned. On this route three kinds are confirmed in the analysis.
| 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. | To be confirmedNo matter document store is described; NetDocuments can be linked. | Confirmed in the analysis |
| 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. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | Held in partObjects can carry user-defined metadata and tags as name and value pairs. | To be confirmed | Confirmed in the analysis |
What the plans mean
- Confirmed in the analysis
- We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.
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.
Soluno 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 Soluno 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 Soluno 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 Soluno
Soluno, which Actionstep now sells as Actionstep Legal Accounting, is an accounting system first, and it expects accounting discipline from the data it is given. Contacts and files need numbers. Entries need dates that fall in open financial periods. Billing, rate and file groups should exist before files are created so that defaults apply. Where documents, calendars and case detail will live is settled alongside.
Numbers for contacts and files
Every contact has a number and every file has a file number, which Soluno can generate on its own or by contact. A firm can keep its old numbers by typing over the suggested value. The format is agreed first, since the help centre puts later number changes behind an administrator setting once NetDocuments is in use.
Groups before files
File, billing and rate groups set the defaults a new file picks up, and a file can override them. Loading thousands of files without the groups in place means fixing each one by hand later. The groups are designed from the source system’s rate tables and billing terms during the analysis.
Periods must be open
Soluno closes financial periods, and a file cannot be closed while it has entries dated after the last closed period. Historic transactions are loaded with the relevant periods open, checked, and then the periods are closed in order. That sequence is rehearsed on the full trial load with the firm’s accountant.
Closed matters need zero balances
A file closes only when it has no work in progress, no receivable and no retainer or trust balance. Old matters that the source system marked closed while still carrying a few dollars will not close here. Those small balances are written off or cleared in the source before extraction, with partner approval.
Documents live beside it
Its help centre covers accounting, banking, billing, contacts and files, and describes links to NetDocuments and to Actionstep practice management. It describes no matter document store. A firm arriving from an all-in-one product should expect to need a second destination for its documents, emails and calendar, and the two loads are planned together so matter numbers match in both.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Soluno 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 Soluno. 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 Soluno 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 Soluno. 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 Soluno
Loaded data is not yet a working system. This is what NewLaw sets up in Soluno, beyond the migration, so that people can work in it from the first day.
Most of the set-up in Soluno is financial structure. The chart of accounts, bank accounts and financial periods come first, then the groups that control billing and rates, then users and what each group of users may do. Lawyers need task code shortcuts and rates before they can enter time. If NetDocuments or Actionstep practice management is to be linked, that connection is made once numbering is final.
Set-up decisions in Soluno
- Chart of accounts, bank accounts and opening financial periods
- File, billing and rate groups with their default arrangements
- Contact and file numbering format, set firm-wide or by contact
- User groups and what each group may see or do
- Task and activity codes and each lawyer’s shortcuts
- Link to NetDocuments or to Actionstep practice management
Questions
Amazon S3 to Soluno: 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 Soluno?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Amazon S3 before the plan is fixed. Documents that have no place in Soluno are exported into folders by client and matter.
Does everything in Amazon S3 have a place in Soluno?
Most of it does on paper. Documents, emails and custom fields could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Soluno is kept as a readable archive, and you see which before the move.
What has to be decided before Amazon S3 data is loaded into Soluno?
Documents, emails and custom fields are confirmed in the analysis. 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 Soluno
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 Soluno are the names and marks of their owners, used here only to identify the two systems.
Moving from Amazon S3 to Soluno?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.