Data migration route
Dropbox Sign data to Full data export
Dropbox Sign is a cloud e-signature service, and Full data export is a store of data kept as files the firm holds. What lands in Full data export is the register: every file’s name, place, dates and details, with the files themselves stored beside it.
Dropbox SignCloud- Documents: Exported in full
- Custom fields: Exported with mapping
- Templates: Exported with mapping
- Intake: Exported with mapping
Full data exportFiles- 1 carried
- 3 mapped
What moves
What moves from Dropbox Sign to Full data export
Each row is a kind of record Dropbox Sign holds, whether Full data export has a place for it, and what is planned. On this route one kind of record carries across and three kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldSignature requests and their completed PDFs, each with an audit trail. | Has a placeFiles under their original names, in client and matter folders. | Exported in full |
| Custom fieldsFields and record types the firm added itself | Held in partResponse data from a signature request can be downloaded as CSV. | Has a placeExtra columns under their original field names. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | HeldReusable templates and template links with preset signer roles and fields. | Has a place in partTemplate files only; the merge fields in them will not run. | Exported with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partDropbox Forms collects answers from clients and can export them to CSV. | Has a place in partAn enquiries table, where the source tracked leads. | Exported with mapping |
What the plans mean
- Exported in full
- Full data export has a place for this kind of record. It is loaded there and checked against Dropbox Sign.
- Exported with mapping
- Full data export 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
The files, and a register of what each one is.
A database is a poor place to keep documents and a good place to keep facts about them. On this route the files from Dropbox Sign are exported to storage the firm controls, and Full data export receives the register: one row per file, with its path, size, dates, author and whatever profile or folder details existed. That register is what makes a large export searchable. It also proves completeness, since the row count and total size can be agreed to the source.
How useful the register is depends on how much Dropbox Sign knows about each file. A document management system has a profile to carry. A plain folder has only a path and dates, and the client or matter has to be read out of folder names. Where versions or an audit history exist, each becomes a table of its own. The export is checked by picking documents at random in the source, finding them through Full data export, and opening the file to confirm it is the same one.
Dropbox Sign is hosted by its maker and Full data export sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Dropbox Sign will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving Dropbox Sign
What a firm has in Dropbox Sign is a pile of executed documents and the proof of how each was signed. The work is getting every completed request out with its audit trail, matching each one to a client and matter, and filing it where the firm keeps its documents. Templates are rebuilt in the new signing tool.
The audit trail travels attached
Each completed request has an audit trail that timestamps events from submission to final signature and includes a hash of the PDF. By default it is appended to the signed document. Team plans can have it returned as a separate file. Either way it is kept with the document, since it is the record of how the signing happened.
Bulk download needs the API
In the web app, documents are downloaded one signature request at a time. Dropbox’s own guidance for downloading everything is to list every request through the API and fetch the files for each. On Premium team plans, cloud sync can instead copy all the team’s documents to a folder in Dropbox, Google Drive, OneDrive or Box.
Nothing says which matter
A signature request has a title, signers and dates. It has no matter number unless someone typed one into the title. Matching thousands of signed PDFs to matters is done from the signer’s email address, the title and the date, and the ones that cannot be matched are listed for the firm.
Requests still out for signature
A request that is waiting on a signer at cutover cannot be handed to another signing service half signed. It is either chased to completion in the old account or cancelled and sent again from the new tool. The list of open requests is drawn up well ahead of cutover so there is time to chase them.
Templates and embedded signing
Templates hold the field positions and signer roles for documents the firm sends often. Each is rebuilt in the new signing tool, unless the analysis finds a format both products accept. If the practice system or website calls the Dropbox Sign API to send documents, that connection is replaced as well.
Where it is going
Arriving in Full data export
A full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.
Tables that still join up
Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.
Documents with an index
Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.
Reports a person can read
Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.
What an export does not keep
Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.
Checked while the source is open
Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what Dropbox Sign holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything Dropbox Sign holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to Full data export as a trial and checked against Dropbox Sign: record counts, totals where Dropbox Sign holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in Dropbox Sign, the export is run a final time and checked again. There is nothing to go live. Dropbox Sign is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
Fixed price, agreed after the analysis. How NewLaw moves legal data
Start
Start this migration
Tell us what is in Dropbox Sign 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 Dropbox Sign holds
What is in it, how its records link, and where each piece would sit in Full data export. 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
Full data export is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.
What is agreed and set up
- Folder layout for tables, documents and reports
- What the key to tables, columns and identifiers records
- Where the copies are stored and who is custodian
- Who may open it, as approved by a partner
- Which look-ups staff must be able to do unaided
- Retention period and the date it is next reviewed
Questions
Dropbox Sign to Full data export: what firms ask
Can we still rely on documents signed in Dropbox Sign after we stop using it?
A completed PDF is a file the firm holds, and it stays readable without the account. What supports it later is the audit trail, which records the signing events and a hash of the document. That is why each document is exported with its trail attached or beside it, and both are filed against the matter.
Is this the same as HelloSign?
It is. HelloSign, HelloSign API and HelloFax were renamed Dropbox Sign, Dropbox Sign API and Dropbox Fax, and the old web address now leads to the Dropbox Sign site. Documents signed under the old name sit in the same account and are exported in the same way.
Can the signed documents go straight into our practice system?
They can be filed there if each one can be tied to a matter. Where the destination stores documents against matters, the signed PDFs are loaded into a signed-documents folder on each. If it does not hold documents at all, they go to the firm’s document store and the matter links to that folder.
Does the copy in Full data export hold documents from Dropbox Sign?
Yes. Files under their original names, in client and matter folders. Documents are written out with the rest, and counts and totals are agreed to the reports in Dropbox Sign as at the export date.
Does everything in Dropbox Sign have a place in Full data export?
On paper, yes: each kind of record Dropbox Sign holds has a place in Full data export. 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 Dropbox Sign is written out to Full data export?
Custom fields, templates and intake records are exported with mapping, so each mapping is agreed with you first. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from Dropbox Sign and into Full data export
Other destinations from Dropbox Sign
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.
Dropbox Sign and Full data export are the names and marks of their owners, used here only to identify the two systems.
Moving from Dropbox Sign to Full data export?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.