Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

Dropbox Sign to Google Drive migration

Dropbox Sign is a cloud e-signature service, and Google Drive is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.

FromDropbox SignCloud
  1. Documents: Carried across
  2. Templates: Carried with mapping
ToGoogle DriveCloud
  1. Custom fields: Kept as a readable archive
  2. Intake: Kept as a readable archive
Readable archiveNo place in Google Drive
  • 1 carried
  • 1 mapped
  • 2 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Dropbox Sign to Google Drive

Each row is a kind of record Dropbox Sign holds, whether Google Drive has a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping and two kinds have no place in Google Drive and are archived.

Records in Dropbox Sign and their place in Google Drive
RecordIn Dropbox SignIn Google DriveWhat is planned
DocumentsFiles stored in or linked from the systemHeldSignature requests and their completed PDFs, each with an audit trail.Has a placeAny file type, stored as uploaded or converted to Google formats.Carried across
Custom fieldsFields and record types the firm added itselfHeld in partResponse data from a signature request can be downloaded as CSV.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationHeldReusable templates and template links with preset signer roles and fields.Has a place in partPrecedents load as files; the load does not rebuild Word automation in Docs.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partDropbox Forms collects answers from clients and can export them to CSV.No placeKept as a readable archive

What the plans mean

Carried across
Google Drive has a place for this kind of record. It is loaded there and checked against Dropbox Sign.
Carried with mapping
Google Drive 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
Google Drive has no place for it. It is exported in a format that opens without Dropbox Sign 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

An export the firm can open without the system.

Google Drive holds files, and most of what Dropbox Sign holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used Dropbox Sign, by client or by year, with a short index file saying what is where.

Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in Google Drive is limited before the export is copied in.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Dropbox Sign 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 Dropbox Sign is kept running until the checks on Google Drive are finished.

Where the data is now

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving off Dropbox Sign

Where it is going

Putting a firm’s matter files into Google Drive means choosing shared drives over personal ones and then deciding how many shared drives there should be. That second decision is driven by Google’s limits and by who is allowed to see what, since access is granted mainly at the level of the whole shared drive.

  1. Shared drives, not My Drive

    Files loaded into a shared drive belong to the firm and remain when the person who loaded them leaves. Anything loaded into someone’s My Drive belongs to that person. Matter files therefore go to shared drives, and My Drive is left for personal working papers.

  2. One drive cannot hold everything

    Google caps a shared drive at 500,000 items, counting folders, shortcuts and anything in the trash, and at 100 levels of nested folders. A firm with twenty years of matters can pass the item cap in a single drive. The split is planned up front, commonly by practice group, or by open and closed matters.

  3. Membership is the main control

    Every member of a shared drive can see all of it unless a Manager restricts a particular folder. Matters that only certain people may open are simpler to protect in a shared drive of their own. The firm supplies the list of restricted matters and partners’ private folders before the drives are created.

  4. The daily upload limit

    Each user can upload 750 GB to Drive in 24 hours, and then has to wait. For a large document set that limit sets the shortest time the load can take. The total size is measured in the analysis, so the firm knows before the freeze whether its documents fit inside a weekend.

  5. Keep Office files as Office files

    Word and Excel files can be stored in Drive as they are or converted to Google formats. Unless the firm asks otherwise they are loaded unconverted, so court documents and automated precedents arrive as they left. The firm decides afterwards which templates are worth rebuilding as Google Docs.

More about moving into Google Drive

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Google Drive on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Dropbox Sign holds and how it is organised, then agree with you where each kind of record will sit in Google Drive. Anything with no place there stays behind or is archived, and you see which before the move.

  2. 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.

  3. Trial load

    A trial is loaded into Google Drive and checked against Dropbox Sign: 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.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in Dropbox Sign, a final pass over a weekend picks up what changed since the trial. Dropbox Sign 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 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

Step 1 of 5: Start with the route

Moving fromDropbox Sign
Moving toGoogle Drive

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what Dropbox Sign holds

    What is in it, how its records link, and where each piece would sit in Google Drive. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. 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

Google Drive 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 Drive set-up for a law firm is a small number of deliberate choices made in the Workspace Admin console and then left alone. Which shared drives exist, who manages each, whether staff may share outside the firm, and whether people work from the browser or from Drive for desktop. Staff also need to be shown where a new matter folder goes.

What is agreed and set up

  • Shared drives by practice group, with a naming pattern
  • Managers and member access levels for each shared drive
  • External sharing rules set in the Admin console
  • Drive for desktop on PCs that need Explorer access
  • A standard subfolder set copied into every new matter
  • Transfer of leavers’ My Drive files as a standing procedure

Questions

Dropbox Sign to Google Drive: 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.

Do documents from Dropbox Sign keep their folders and dates in Google Drive?

Google Drive stores documents. Any file type, stored as uploaded or converted to Google formats. 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 Google Drive has no place for?

On this route that is custom fields and intake records. They are exported from Dropbox Sign 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 Dropbox Sign data is loaded into Google Drive?

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.

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.

How we do itDiscovery to rollout, step by step

Dropbox Sign and Google Drive are the names and marks of their owners, used here only to identify the two systems.

Moving from Dropbox Sign to Google Drive?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.