Data migration route
DocuWare to Dropbox migration
DocuWare is a document management system, and Dropbox is cloud file storage. Storage only has folders, so the move decides what of each document’s profile is kept in names and what in an index.
DocuWareDocument management- Documents: Carried across
- Emails: Carried with mapping
- Notes: Carried with mapping
- Tasks: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
DropboxCloud- Custom fields: Kept as a readable archive
- 1 carried
- 2 mapped
- 3 to confirm
- 1 archived
What moves
What moves from DocuWare to Dropbox
Each row is a kind of record DocuWare holds, whether Dropbox has a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping, one kind has no place in Dropbox and is archived and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldIn file cabinets, found by index fields. One document may contain several files. | Has a placeFiles in folders; the folder path is the only index. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partAn email can be stored with its attachments as one document. | Has a place in partAs .msg or .eml files filed in the matter folder. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | Held in partAnnotations and stamps are stored with the document, on layers over the file. | Has a place in partAs documents saved to the matter folder. | Carried with mapping |
| TasksTo-dos and workflow steps assigned to people | To be confirmedWorkflow tasks exist where workflow has been configured. | No place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldIndex fields are defined separately for each file cabinet. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partPrecedents load as ordinary files in a precedents folder. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | No place | Confirmed in the analysis |
What the plans mean
- Carried across
- Dropbox has a place for this kind of record. It is loaded there and checked against DocuWare.
- Carried with mapping
- Dropbox holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
- 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.
- Kept as a readable archive
- Dropbox has no place for it. It is exported in a format that opens without DocuWare 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
Profiles flatten into folders and an index.
A document management system knows things about a file that a folder cannot hold: its profile, its versions, who may open it. Moving from DocuWare to Dropbox flattens that. Client and matter become folder levels. Document type may become a subfolder. Versions become separate files with a suffix, or only the latest is kept. Each of these is a choice the firm makes before the export, and the result is tested on a sample of real matters.
What the folders cannot carry goes into an index: a spreadsheet listing every exported file with its document number, author, dates, type and original location. With it, a document cited by number in an old email can still be found. Access restrictions do not transfer by themselves. Restricted workspaces are exported to separate folders, and permissions are set on those in Dropbox before anyone else is given access.
How DocuWare is run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of DocuWare 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 DocuWare is kept running until the checks on Dropbox are finished.
Where the data is now
Leaving DocuWare
DocuWare is organised for retrieval by index, so an export is a set of documents plus a table of index values, one table per file cabinet. There may be no folder structure at all. The move turns index fields into whatever the destination files by, which for a legal system means deriving a client and matter for every document from fields that were designed for something else.
Each file cabinet stands alone
Every file cabinet has its own index fields. An invoices cabinet might have supplier, date and amount, while a correspondence cabinet has a matter number and document type. Each is mapped separately, and some, such as supplier invoices, may belong with the accounts system’s records and not in the matter files at all.
One document, several files
A DocuWare document can hold up to 999 files clipped together: a scanned letter, a Word reply, an email with attachments. Most destinations store one file per document. The plan says whether a clipped set becomes one merged PDF, a group of related documents or a folder.
Scans are PDF/A, the rest native
Paper scanned through DocuWare is stored as PDF/A, while Office and PDF files are kept in their original format. Scanned items depend on a full-text index to be searchable. If the destination will not run its own text recognition, the text has to travel with the file, which is checked on a sample.
Storage changed at version 7
On-premises systems that began on version 6 or earlier have documents in two layouts: older ones with an XML header file and numbered file names, newer ones with index data in the database and file names that are GUIDs. The route for extraction is chosen in the analysis with both layouts in mind, so that nothing depends on guessing which one a document uses.
Document trays
Items that were scanned or imported but never indexed sit in users’ document trays, outside every file cabinet. Users are asked to store or delete them before the freeze. Whatever is left is listed by user, so nothing is lost by oversight.
Where it is going
Arriving in Dropbox
Loading matter files into Dropbox is a matter of getting the tree right, since the tree is all there is. No field holds a matter number or a client name. The folder names carry that, so the naming rule is agreed first: what a client folder is called, what a matter folder is called, and which subfolders every matter gets.
Team folders before files
Team folders are shared with groups, and each group is given an editor or view-only role. The groups and the top-level folders are created before the load so that files arrive already restricted. Loading first and sharing afterwards leaves a period in which the wrong people can see everything.
Keep paths under 260 characters
Dropbox’s naming guidance asks for full paths shorter than 260 characters. Matter trees from document systems often exceed that once the client name, matter description and subfolders are joined. Long paths are measured early and cut back by rule, usually by trimming the matter description and keeping the number.
Characters that get swapped
On Windows, the desktop app replaces restricted characters in names with an underscore. A file called Smith v Jones: Affidavit becomes something slightly different on some machines. Names are cleaned before loading so that the file has one name everywhere and matches the index kept from the old system.
Matter data has nowhere to go
Parties, matter type, responsible lawyer, open and closed dates: none of it has a field here. If the firm is leaving a practice management system and keeping only documents, that data can be kept as an exported spreadsheet beside the folders, so they can still be read against it. Whether one is produced is decided in the analysis.
History starts on loading day
Version history in Dropbox begins when a file arrives. Earlier versions from the old system come across as separately named files in the matter folder, or stay behind. The firm sees a sample matter loaded with its earlier versions as named copies before choosing.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Dropbox on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what DocuWare holds and how it is organised, then agree with you where each kind of record will sit in Dropbox. 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 Dropbox and checked against DocuWare: 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 DocuWare, a final pass over a weekend picks up what changed since the trial. DocuWare 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 DocuWare 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 DocuWare holds
What is in it, how its records link, and where each piece would sit in Dropbox. 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
Dropbox 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.
Beyond the load, a firm on Dropbox needs the account arranged so the files belong to the firm and not to individuals. That means a team plan with an administrator, groups that match how the firm works, and a decision about which folders sync to every computer. A written filing rule tells staff where each new matter folder goes.
What is agreed and set up
- Team folders for clients, precedents and administration
- Groups by team, each with an editor or viewer role
- Which folders sync to PCs and which stay online-only
- Rules for sharing links and folders with clients
- A written naming rule for client and matter folders
- Steps for removing a leaver without losing their folders
Questions
DocuWare to Dropbox: what firms ask
Our DocuWare has no folders. How will documents be filed in the new system?
From the index. If a file cabinet has a matter or client number field, documents are filed by it. If it has only names or dates, the values are matched to the matter list and the unmatched are reported. Document type fields usually become folders or categories in the destination.
Can stamps and annotations be kept?
DocuWare keeps annotations and stamps as layers over the file, not inside it. To keep an approval stamp visible elsewhere, it has to become part of a PDF copy, and whether DocuWare can produce that copy in bulk is confirmed in the analysis. The firm chooses, for each file cabinet, whether to take the original, the stamped copy, or both.
Do documents from DocuWare keep their folders and dates in Dropbox?
Dropbox stores documents. Files in folders; the folder path is the only index. 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 Dropbox has no place for?
On this route that is custom fields. They are exported from DocuWare 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 DocuWare data is loaded into Dropbox?
Emails and notes are carried with mapping, so each mapping is agreed with you first. Tasks, templates and intake records 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 DocuWare and into Dropbox
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.
DocuWare and Dropbox are the names and marks of their owners, used here only to identify the two systems.
Moving from DocuWare to Dropbox?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.