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

Data migration route

HelloSign data to SQLite

HelloSign is a cloud e-signature service, and SQLite is a store of data kept as files the firm holds. What lands in SQLite is the register: every file’s name, place, dates and details, with the files themselves stored beside it.

FromHelloSignCloud
  1. Intake: Exported in full
  2. Documents: Exported with mapping
  3. Custom fields: Exported with mapping
ToSQLiteFiles
  1. Templates: Kept as a readable archive
Readable archiveNo place in SQLite
  • 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 SQLite

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

Records in HelloSign and their place in SQLite
RecordIn HelloSignIn SQLiteWhat is planned
DocumentsFiles stored in or linked from the systemHeldRequests sent in the HelloSign years sit in the current Dropbox Sign account.Has a place in partListed in a table; the files themselves stay in folders beside the database.Exported with mapping
Custom fieldsFields and record types the firm added itselfHeld in partData typed into fields by signers is kept with the request.Has a placeColumns added to the table they belonged to.Exported with mapping
TemplatesPrecedents, document templates and automationHeldTemplates built under the HelloSign name remain in the account.No placePrecedent files are kept in folders, not in the database.Kept as a readable archive
IntakeLeads, enquiries, intake forms and pipelinesHeld in partHelloWorks forms, now offered as Dropbox Forms.Has a placeAn enquiries table, where the source tracked them.Exported in full

What the plans mean

Exported in full
SQLite has a place for this kind of record. It is loaded there and checked against HelloSign.
Exported with mapping
SQLite 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
SQLite 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

The files, and a register of what each one is.

A database is a poor place to keep documents and a good place to keep facts about them. On this route the files from HelloSign are exported to storage the firm controls, and SQLite receives the register: one row per file, with its path, size, dates, author and whatever profile or folder details existed. That register is what makes a large export searchable. It also proves completeness, since the row count and total size can be agreed to the source.

How useful the register is depends on how much HelloSign knows about each file. A document management system has a profile to carry. A plain folder has only a path and dates, and the client or matter has to be read out of folder names. Where versions or an audit history exist, each becomes a table of its own. The export is checked by picking documents at random in the source, finding them through SQLite, and opening the file to confirm it is the same one.

HelloSign is hosted by its maker and SQLite sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What HelloSign will release depends on its export tools, and that is confirmed in the analysis.

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

A SQLite archive suits a firm that wants the old system’s records kept, seldom consulted, and free of any server or subscription. Everything structured goes into one file. That simplicity moves the responsibility elsewhere: the file has no security of its own and no administrator watching it, so where it is stored and who can reach it are the real decisions.

  1. One file, kept with the archive

    Matters, contacts, time, invoices and trust transactions become tables in a single file. It is stored with the firm’s closed-matter records and can be copied like any document. A checksum recorded when the file is finalised lets anyone confirm, years later, that the copy they hold has not been altered, and the firm decides whether to keep one.

  2. No logins inside the file

    SQLite has no users or passwords. Anyone who can open the file can read every client’s ledger. Protection comes from where it is kept, such as a restricted folder or an encrypted volume, and that choice is the firm’s. It can suit an archive consulted by two people, and it is said plainly so nobody assumes otherwise.

  3. Built for reading, not sharing

    Only one program can write to the file at a time, and SQLite’s authors point people to a client/server database where many users share data over a network. A finished archive never meets that limit. It is the reason SQLite is used here for records that are closed and not for anything staff still update.

  4. Documents stay outside it

    Documents remain ordinary files in matter folders, and a table in the database lists each one with its matter, title, dates and path. Keeping them as files means they open with a double-click and can be handed to a client. The table is how a file is found by matter number instead of by guessing its name.

  5. Someone has to open it

    SQLite publishes its own command-line program for opening a database file, and other tools read the format too. None of that helps if nobody remembers how. Saved queries for the usual look-ups and a short note on which tool to use can sit in the same folder as the file, and the firm decides what it needs.

More about moving into SQLite

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what HelloSign holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything HelloSign holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to SQLite as a trial and checked against HelloSign: record counts, totals where HelloSign holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in HelloSign, the export is run a final time and checked again. There is nothing to go live. HelloSign is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

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 toSQLite

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

Structure, permissions and handover

SQLite is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

There is nothing to install on a server and nothing to license. The work is in making the file usable and safe to keep: naming it, documenting its tables, storing it where the firm’s records policy says archives go, and checking that a member of staff can open it and find a matter. Whether a second copy is held somewhere separate is the firm’s call.

What is agreed and set up

  • File name, storage location and whether a second copy exists
  • Whether a checksum is recorded for later verification
  • Saved queries for matter, ledger and document look-ups
  • Which tool staff will use to open the file
  • Who may open the folder the file sits in
  • Retention period and destruction date noted beside the file

Questions

HelloSign to SQLite: 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.

Does the copy in SQLite hold documents from HelloSign?

In part. Listed in a table; the files themselves stay in folders beside the database. What SQLite can hold is written out once its mapping is agreed, and the rest is kept beside the data as files that open without HelloSign.

What happens to records SQLite has no place for?

On this route that is templates. 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 is written out to SQLite?

Documents and custom fields are exported with mapping, so each mapping is agreed with you first. The firm also decides who may open the archive and how long it is kept.

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

Moving from HelloSign to SQLite?

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

We reply within one business day.