Data migration route
HelloSign to Litify migration
HelloSign is a cloud e-signature service, and Litify is a cloud case management system. This is a narrow move: the records HelloSign holds are matched to the people and matters in Litify.
HelloSignCloud- Documents: Carried across
- Intake: Carried across
- Custom fields: Carried with mapping
- Templates: Carried with mapping
LitifyCloud- 2 carried
- 2 mapped
What moves
What moves from HelloSign to Litify
Each row is a kind of record HelloSign holds, whether Litify has a place for it, and what is planned. On this route two kinds of record carry across and two kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldRequests sent in the HelloSign years sit in the current Dropbox Sign account. | Has a placeLoaded to the document component and attached to matters. | Carried across |
| Custom fieldsFields and record types the firm added itself | Held in partData typed into fields by signers is kept with the request. | Has a placeCustom fields are created before loading. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldTemplates built under the HelloSign name remain in the account. | Has a place in partTemplates are rebuilt in Litify’s document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partHelloWorks forms, now offered as Dropbox Forms. | Has a placeLoaded as intakes. | Carried across |
What the plans mean
- Carried across
- Litify has a place for this kind of record. It is loaded there and checked against HelloSign.
- Carried with mapping
- Litify 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 Litify, 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 Litify 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 Litify are finished.
Where the data is now
Leaving HelloSign
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.
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.
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.
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.
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.
Where it is going
Arriving in Litify
Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.
The design comes first
Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.
One party, many roles
Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.
Open enquiries load as intakes
Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.
Documents load after records
Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.
Validation rules reject bad rows
A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Litify on this route, which makes it repeatable: a load can be run again until it is right. The maker of Litify 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.
Analysis
We read what HelloSign holds and how it is organised, then agree with you where each kind of record will sit in Litify. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into Litify 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.
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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what HelloSign holds
What is in it, how its records link, and where each piece would sit in Litify. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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 Litify
Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.
A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.
Set-up decisions in Litify
- Define intake questionnaires and the rules for conversion
- Set case types, matter stages and page layouts
- Build matter plans that create tasks at each stage
- Design document folders and generation templates per case type
- Configure user roles and sharing for restricted matters
- Decide on timekeeping, billing and accounting integrations
Questions
HelloSign to Litify: 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 Litify?
Litify stores documents. Loaded to the document component and attached to matters. 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 Litify?
On paper, yes: each kind of record HelloSign holds has a place in Litify. 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 Litify?
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.
Other routes
Other routes from HelloSign and into Litify
Other destinations from HelloSign
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
HelloSign and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from HelloSign to Litify?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.