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

Data migration route

HelloSign to Neos migration

HelloSign is a cloud e-signature service, and Neos is a cloud case management system for personal injury work. This is a narrow move: the records HelloSign holds are matched to the people and matters in Neos.

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

What moves

What moves from HelloSign to Neos

Each row is a kind of record HelloSign holds, whether Neos 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 HelloSign and their place in Neos
RecordIn HelloSignIn NeosWhat is planned
DocumentsFiles stored in or linked from the systemHeldRequests sent in the HelloSign years sit in the current Dropbox Sign account.Has a placeCase Docs tab, organised in sub-tabs.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 placeUser-defined fields are created on the relevant tab first.Carried with mapping
TemplatesPrecedents, document templates and automationHeldTemplates built under the HelloSign name remain in the account.Has a place in partTemplates are rebuilt for Neos document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partHelloWorks forms, now offered as Dropbox Forms.Has a placeIntakes tab. Simple intake imports from CSV are supported.Carried across

What the plans mean

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

Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.

  1. Every figure needs a value code

    Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.

  2. Lists are set up first

    Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.

  3. Documents go to sub-tabs

    Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.

  4. Reminders split two ways

    Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.

  5. Assembly runs its own conversions

    Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.

More about moving into Neos

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Neos on this route, which makes it repeatable: a load can be run again until it is right. The maker of Neos says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in HelloSign and checking each trial against HelloSign.

  1. Analysis

    We read what HelloSign holds and how it is organised, then agree with you where each kind of record will sit in Neos. 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 Neos 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 toNeos

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

Loaded data is not yet a working system. The maker of Neos runs or arranges the set-up of its product, so this is what has to be decided and put in place in Neos, whoever does the work, before people rely on it from the first day.

Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.

Set-up decisions in Neos

  • Set case types, statuses and staff roles
  • Agree the value code list with accounts staff
  • Build checklists for each case type and stage
  • Create user-defined fields for data the tabs lack
  • Prepare document templates for the generation wizard
  • Connect Microsoft 365, QuickBooks and the phone system

Questions

HelloSign to Neos: 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 Neos?

Neos stores documents. Case Docs tab, organised in sub-tabs. 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 HelloSign have a place in Neos?

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

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

Moving from HelloSign to Neos?

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

We reply within one business day.