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

Data migration route

HelloSign to iManage Cloud migration

HelloSign is a cloud e-signature service, and iManage Cloud 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
ToiManage CloudCloud
  1. Intake: Kept as a readable archive
Readable archiveNo place in iManage Cloud
  • 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 iManage Cloud

Each row is a kind of record HelloSign holds, whether iManage Cloud 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 iManage Cloud and is archived.

Records in HelloSign and their place in iManage Cloud
RecordIn HelloSignIn iManage CloudWhat is planned
DocumentsFiles stored in or linked from the systemHeldRequests sent in the HelloSign years sit in the current Dropbox Sign account.Has a placeEach needs a workspace and valid client and matter values; its class sets default security.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 place in partA fixed number of custom profile fields, each a validated list.Carried with mapping
TemplatesPrecedents, document templates and automationHeldTemplates built under the HelloSign name remain in the account.Has a place in partPrecedents load as documents. Automation is rebuilt in the firm’s drafting tools.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
iManage Cloud has a place for this kind of record. It is loaded there and checked against HelloSign.
Carried with mapping
iManage Cloud 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
iManage Cloud 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.

iManage Cloud 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 iManage Cloud 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 iManage Cloud 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

Administrators of an iManage Cloud library have API access only, so nothing is loaded by writing to a database. For cloudimanage.com, the newer of its two cloud platforms, iManage lists a supervised import API, sync APIs and a metadata loader. Nothing can be filed loose: every document goes into a workspace, with valid client and matter values. So the client and matter lists, the workspace template and the security groups are built first.

  1. Client and matter lists first

    Custom1 and custom2 are validated lists, with each matter a child of its client. A value that is not already in the list cannot be assigned to a document. The lists are loaded from the practice management system or the old document store before any content, closed matters with documents included.

  2. One workspace per matter

    Each matter gets a workspace generated from a template, so the template is designed before migration: its tabs, its folders, which are created up front and which on demand. Old folder trees rarely match it. The mapping says where each old folder lands and what happens to folders with no equivalent.

  3. Authors must be known users

    Author and operator are profile fields tied to users of the library. Documents written by people who left years ago need a decision: recreate those people as inactive users, or assign a placeholder author. That choice affects searching by author for as long as the firm uses the system.

  4. Hybrid security

    iManage calls its security model hybrid: where a user’s groups disagree, the most permissive access applies unless one of them is denied. On cloudimanage.com that model cannot be changed. Default security is normally set on the workspace and inherited below it. Restricted matters from the old system are loaded with their access list already in place.

  5. New numbers, original dates

    Documents are numbered by iManage as they are loaded, so old numbers do not carry over as numbers. On cloudimanage.com the file date setting is fixed to the file’s own date, and on imanage.work it can be set either way. Which dates display is checked on the trial load. The old reference can be carried in a custom field or the description where the firm wants to search by it.

More about moving into iManage Cloud

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in iManage Cloud 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 iManage Cloud. 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 iManage Cloud 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 toiManage Cloud

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 iManage Cloud. 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 iManage Cloud

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

Setting up iManage Cloud is mostly design work done before any user logs in: how many libraries, what a workspace looks like, which profile fields are captioned for what, and who can see which matters. Then come the links that keep it running day to day, such as creating a workspace when a matter is opened in the practice management system, and the add-ins on each desk.

Set-up decisions in iManage Cloud

  • Library structure and captions for client, matter and other fields
  • Workspace templates, folder names and Flexible Folders rules by practice area
  • Document classes, subclasses and the profile fields each one requires
  • Roles, groups, default security and walls for restricted matters
  • Workspace creation fed from the practice management system’s matter list
  • Work Desktop, Outlook email filing and Mobility on each device, with training

Questions

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

iManage Cloud stores documents. Each needs a workspace and valid client and matter values; its class sets default security. 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 iManage Cloud 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 iManage Cloud?

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

Moving from HelloSign to iManage Cloud?

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

We reply within one business day.