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

Data migration route

Dropbox Sign to Centerbase migration

Dropbox Sign is a cloud e-signature service, and Centerbase is a cloud practice management system. This is a narrow move: the records Dropbox Sign holds are matched to the people and matters in Centerbase.

FromDropbox SignCloud
  1. Documents: Carried across
  2. Intake: Carried across
  3. Custom fields: Carried with mapping
  4. Templates: Carried with mapping
ToCenterbaseCloud
  • 2 carried
  • 2 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Dropbox Sign to Centerbase

Each row is a kind of record Dropbox Sign holds, whether Centerbase has a place for it, and what is planned. On this route two kinds of record carry across and two kinds need mapping.

Records in Dropbox Sign and their place in Centerbase
RecordIn Dropbox SignIn CenterbaseWhat is planned
DocumentsFiles stored in or linked from the systemHeldSignature requests and their completed PDFs, each with an audit trail.Has a placeInto Document Storage, or left in a connected NetDocuments, iManage or SharePoint store.Carried across
Custom fieldsFields and record types the firm added itselfHeld in partResponse data from a signature request can be downloaded as CSV.Has a placeCreated and placed on page layouts before records are loaded.Carried with mapping
TemplatesPrecedents, document templates and automationHeldReusable templates and template links with preset signer roles and fields.Has a place in partTemplates are rebuilt to merge Centerbase client and matter data.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partDropbox Forms collects answers from clients and can export them to CSV.Has a placeEnquiries are held as Potential New Client records; loading open ones is confirmed in the analysis.Carried across

What the plans mean

Carried across
Centerbase has a place for this kind of record. It is loaded there and checked against Dropbox Sign.
Carried with mapping
Centerbase 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

A narrow move, checked like a large one.

A source like Dropbox Sign holds one kind of record well: an address book, a calendar, a set of signed documents. None of it is organised by matter. The work is matching each contact to a contact in Centerbase, and each appointment or signed document to the matter it belongs to. Where a match cannot be made from a name, an email address or a reference, the record is listed for the firm to place by hand or leave behind.

The volume is small and the load is quick, which makes it tempting to skip the checks. They still apply. Contacts are compared with what Centerbase already holds, so the move does not create a second copy of every client. Dates are checked for time zones, a common fault in calendar data. Signed documents arrive with their completion date and, where the service provides one, the audit record as a separate file.

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 Centerbase 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

Centerbase takes practice, billing, trust and accounting data together, so loading a firm into it is a finance project as much as a matter load. Clients come first because matters inherit from them. The chart of accounts, bank accounts and accounting basis are fixed before balances go in. Because the product is configured per firm, the fields and layouts are designed before the trial load, not after.

  1. Clients carry the billing rules

    Billing arrangements, rates and accounting preferences are held on the client and passed to its matters. Source systems that create a fresh client for every matter leave duplicates behind. Those are merged during clean-up, so that each real client exists once and its terms are set in one place.

  2. The ledger comes too

    Centerbase has a full general ledger and runs on a cash or accrual basis. A firm arriving from a billing system with QuickBooks beside it is consolidating two sets of records. The accountant decides the basis and the opening date, and the trial balance loaded is agreed to the old books.

  3. Trust and retainers are separate

    A matter can hold multiple trust and retainer accounts. Source systems often blur the two, recording an advance on fees as trust or the reverse. Each balance is classified before loading, and client-level funds that were never tied to a matter are assigned to one or held at client level.

  4. Decide the document home

    Documents can go into built-in Document Storage, or stay in NetDocuments, iManage or SharePoint and be connected. Centerbase can create a standard folder structure when a matter is opened. That structure is agreed first, so migrated documents are filed into the same folders that new matters will get.

  5. Fields are designed, not assumed

    With unlimited custom fields, nearly every source field can have a home. That is a reason for restraint. Each one must be created and placed on a layout, and a page crowded with unused fields slows people down. The firm chooses which fields earn a place and which become a note.

More about moving into Centerbase

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Centerbase 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 Centerbase. 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 Centerbase 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 toCenterbase

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

Setting up Centerbase

Loaded data is not yet a working system. This is what NewLaw sets up in Centerbase, beyond the migration, so that people can work in it from the first day.

Setting up Centerbase is largely configuration. Bill templates, rate tables and the pre-bill approval chain have to match how the firm bills today, or the first billing cycle exposes the gaps. The chart of accounts and bank accounts are built with the finance team. Workflows that open matters, create folders and assign first tasks are written last, once the fields they depend on are settled.

Set-up decisions in Centerbase

  • Bill templates and billing arrangements for each client type
  • Rate tables, timekeepers and the pre-bill approval chain
  • Chart of accounts, bank accounts and cash or accrual basis
  • Custom fields, page layouts and automated workflows by practice
  • Document storage choice and the standard matter folder structure
  • Outlook and Microsoft 365 connection for email and calendar

Questions

Dropbox Sign to Centerbase: 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 Centerbase?

Centerbase stores documents. Into Document Storage, or left in a connected NetDocuments, iManage or SharePoint store. 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.

Does everything in Dropbox Sign have a place in Centerbase?

On paper, yes: each kind of record Dropbox Sign holds has a place in Centerbase. 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 data is loaded into Centerbase?

Custom fields 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.

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 Centerbase are the names and marks of their owners, used here only to identify the two systems.

Moving from Dropbox Sign to Centerbase?

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

We reply within one business day.