Data migration route
Box to Sync.com migration
Box and Sync.com are both cloud file storage. The folders move as they are, and the work is in permissions, paths and links.
BoxCloud- Documents: Carried across
- Emails: Carried with mapping
- Notes: Carried with mapping
- Templates: Carried with mapping
Sync.comCloud- Tasks: Kept as a readable archive
- Custom fields: Kept as a readable archive
- 1 carried
- 3 mapped
- 2 archived
What moves
What moves from Box to Sync.com
Each row is a kind of record Box holds, whether Sync.com has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping and two kinds have no place in Sync.com and are archived.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldFiles in folders, with version history, comments and optional metadata. | 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 store | Held in partOnly as message files saved or emailed into a folder. | Has a place in partMessage files such as .msg or .eml, filed in the matter’s folder. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | Held in partBox Notes are documents written inside Box, not notes recorded against a matter. | Has a place in partOnly as a document written out to the matter’s folder. | Carried with mapping |
| TasksTo-dos and workflow steps assigned to people | Held in partTasks can be assigned on a file; they are not matter tasks. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | Held in partMetadata templates add fields to files and folders. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | Held in partPrecedents are kept as ordinary files; Box Notes has its own note templates. | Has a place in partPrecedents load as ordinary files. | Carried with mapping |
What the plans mean
- Carried across
- Sync.com has a place for this kind of record. It is loaded there and checked against Box.
- 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 Box 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 Box 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 Box 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 Box is kept running until the checks on Sync.com are finished.
Where the data is now
Leaving Box
Leaving Box is mostly a question of ownership and of what is attached to files but not inside them. Folders belong to whoever created them unless the firm set Box up with administrator-owned folders. Comments, tasks, metadata values and earlier versions live in Box beside each file. A plain download brings the current files and none of the rest.
Every top-level folder has an owner
Box lets either administrators or ordinary users own top-level folders, depending on how the account was set up. Where users own them, matter files are spread across personal accounts, including those of people who have left. The inventory is taken from the administrator’s side so that nobody’s folders are missed.
Each person sees a different tree
A collaborator invited part-way down sees that folder as their own top level. Two lawyers describing the same matter folder may give different paths to it. The structure that moves is the owner’s full tree, and staff are shown where their familiar folders sit within it before go-live.
Box Notes are not Word files
Notes written in Box Notes exist only inside Box. They are not files in the usual sense and do not open in Word. Firms that kept file notes or meeting minutes this way need them converted to a document format before the move, and the conversion is checked on a sample in the trial load.
Shared links point at Box
Clients and other parties may hold links to matter folders or single documents. Those links point at Box and cannot be relied on once the account is closed. A report of links and outside collaborators shows which matters have live external access, so the firm can tell those people where documents will be from cutover.
Versions depend on the plan
How many earlier versions of a file Box keeps is set by the plan and can be reduced by an administrator. What is not there cannot be moved. Where versions do exist, the destination may take them as true versions or only as separately named copies, which is settled in the analysis.
Where it is going
Arriving in Sync.com
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.
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.
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.
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.
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.
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.
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.
Analysis
We read what Box 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.
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 Sync.com and checked against Box: 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 Box, a final pass over a weekend picks up what changed since the trial. Box 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 Box 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 Box 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.
- 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
Box to Sync.com: what firms ask
Do our document versions come across from Box?
Only versions Box still holds can be moved, and that number depends on the plan. How they arrive depends on the destination: a document management system usually has version slots, a plain drive does not. The trial load can show one sample matter both ways if the firm is undecided.
What happens to folders we shared with clients?
The collaborators and shared links belong to Box and do not transfer. Before cutover the firm gets a list of every folder with outside access. If the new system has a client portal or its own sharing, access is set up there, and clients are told where to find their documents from then on.
Can we move only open matters and leave the rest in Box?
Yes, if the folder names or metadata show which matters are open. Where they do not, the open matter list from the practice management system is matched to folders by client and matter number. Closed folders can stay in Box read only for as long as the firm keeps the subscription.
Do documents from Box 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 tasks and custom fields. They are exported from Box 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 Box data is loaded into Sync.com?
Emails, notes and templates 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 Box and into Sync.com
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.
Box and Sync.com are the names and marks of their owners, used here only to identify the two systems.
Moving from Box 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.