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

Data migration route

HelloSign to NetDocuments migration

HelloSign is a cloud e-signature service, and NetDocuments is a cloud document management system. Only files and their details have a place there, so this route carries the documents and archives the rest.

FromHelloSignCloud
  1. Documents: Carried across
  2. Custom fields: Carried with mapping
  3. Templates: Carried with mapping
ToNetDocumentsCloud
  1. Intake: Kept as a readable archive
Readable archiveNo place in NetDocuments
  • 1 carried
  • 2 mapped
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from HelloSign to NetDocuments

Each row is a kind of record HelloSign holds, whether NetDocuments has a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping and one kind has no place in NetDocuments and is archived.

Records in HelloSign and their place in NetDocuments
RecordIn HelloSignIn NetDocumentsWhat is planned
DocumentsFiles stored in or linked from the systemHeldRequests sent in the HelloSign years sit in the current Dropbox Sign account.Has a placeImported with profile values, folder, dates and access set per document.Carried across
Custom fieldsFields and record types the firm added itselfHeld in partData typed into fields by signers is kept with the request.Has a placeAs custom profile attributes, created in the repository before the load.Carried with mapping
TemplatesPrecedents, document templates and automationHeldTemplates built under the HelloSign name remain in the account.Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partHelloWorks forms, now offered as Dropbox Forms.No placeKept as a readable archive

What the plans mean

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

Only the documents have a place here.

NetDocuments is a document management system: it takes files and the details that describe them. Most of what HelloSign holds is not files. Entries, balances, settings and lists have no place in a document store, and the table above is short for that reason. What can move is any document HelloSign produced or stored: invoices as PDFs, signed agreements, attachments, exported reports. Each is filed under the client or matter it relates to.

The useful version of this job is often an archive. A firm retiring a system wants its records readable later without keeping the subscription or the old PC. The data is exported in open formats, spreadsheets and PDFs, and filed in NetDocuments in a workspace set aside for it, with access limited to the people who need it. That gives the firm one place to look, under the same retention rules as the rest of its documents.

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

Where the data is now

A firm leaving HelloSign is leaving Dropbox Sign under its earlier name. The signed documents and their audit trails are exported from the current Dropbox Sign account, tied to the right client and matter, and filed. Accounts opened in the HelloSign years raise a few questions of their own, mostly about old logins and old integrations.

  1. Same account, newer name

    There is no separate HelloSign archive to find. The old web address forwards to the Dropbox Sign site, and the same login opens the same documents. Before any export, the firm confirms which email addresses hold accounts, because an account opened years ago may sit under one person’s address and never have been joined to a team.

  2. Old integrations keep the name

    Practice systems, form builders and document tools that were connected to HelloSign years ago may still show the old name in their settings. Dropbox kept those connections working through the rename. Each one is found and listed, since a connection nobody remembers can go on sending documents through the old account after the firm believes it has left.

  3. Staff who have left

    Documents sent from an individual account belong to that account. If the sender has left the firm and the mailbox is closed, their signed documents may be reachable only by recovering that login, or through a team administrator where the account belonged to a team. Departed senders are identified early so access can be sorted out before the export is run.

  4. Faxes and forms

    HelloFax and HelloWorks were sister products, and some firms used them from the same login. Dropbox now offers them as Dropbox Fax and Dropbox Forms. Faxes and form submissions are not signature requests, so they are looked for separately and exported if the firm still needs them.

More about moving off HelloSign

Where it is going

Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.

  1. Lookup tables before documents

    Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.

  2. Workspaces come from the profile

    A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.

  3. Import files are unforgiving

    The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.

  4. Folder limits and depth

    A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.

  5. Security at the right level

    Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.

More about moving into NetDocuments

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

    We read what HelloSign holds and how it is organised, then agree with you where each kind of record will sit in NetDocuments. 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 NetDocuments and checked against HelloSign: 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 HelloSign, a final pass over a weekend picks up what changed since the trial. HelloSign 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 HelloSign 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 fromHelloSign
Moving toNetDocuments

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 HelloSign holds

    What is in it, how its records link, and where each piece would sit in NetDocuments. 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 NetDocuments

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

Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.

Set-up decisions in NetDocuments

  • Cabinet design: one for the firm, or several by purpose
  • Profile attributes, lookup tables and the client and matter hierarchy
  • Workspace layout with default folders, filters and saved searches
  • User groups, cabinet membership and security for restricted matters
  • A feed of new clients and matters from practice management
  • ndOffice, ndMail and Outlook filing on every desk, with training

Questions

HelloSign to NetDocuments: what firms ask

Does HelloSign still exist?

Only under its newer name. Dropbox renamed it Dropbox Sign in October 2022, and the hellosign.com address now forwards to sign.dropbox.com. The service, the accounts and the documents are the same ones, so a move off HelloSign is planned as a move off Dropbox Sign.

Do documents signed years ago under HelloSign still have their audit trail?

The audit trail is appended to each executed document as part of the PDF, and it includes an identifier Dropbox can use to look up the transaction log. Documents completed before the rename are downloaded like recent ones, trail included, and a sample of the oldest is opened and checked in the trial load.

Do documents from HelloSign keep their folders and dates in NetDocuments?

NetDocuments stores documents. Imported with profile values, folder, dates and access set per document. 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 NetDocuments has no place for?

On this route that is intake records. They are exported from HelloSign 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 HelloSign data is loaded into NetDocuments?

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

HelloSign and NetDocuments are the names and marks of their owners, used here only to identify the two systems.

Moving from HelloSign to NetDocuments?

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

We reply within one business day.