Data migration route
Dropbox Sign to Lawmatics migration
Dropbox Sign is a cloud e-signature service, and Lawmatics is a cloud CRM and intake system. The records move, and the pipeline, forms and automations are set up again in Lawmatics.
Dropbox SignCloud- Intake: Carried across
- Documents: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
LawmaticsCloud- 1 carried
- 3 mapped
What moves
What moves from Dropbox Sign to Lawmatics
Each row is a kind of record Dropbox Sign holds, whether Lawmatics has a place for it, and what is planned. On this route one kind of record carries across and three kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldSignature requests and their completed PDFs, each with an audit trail. | Has a place in partFiles and folders on each matter, added by upload or API, not by the spreadsheet import. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | Held in partResponse data from a signature request can be downloaded as CSV. | Has a placeMatter, contact and company fields. A field must exist before data is imported into it. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldReusable templates and template links with preset signer roles and fields. | Has a place in partDocument and email templates are rebuilt with Lawmatics merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partDropbox Forms collects answers from clients and can export them to CSV. | Has a placePipelines and stages, marketing sources and campaigns. | Carried across |
What the plans mean
- Carried across
- Lawmatics has a place for this kind of record. It is loaded there and checked against Dropbox Sign.
- Carried with mapping
- Lawmatics 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
Contacts and leads move. Forms and automations are rebuilt.
Between two tools that manage contacts and enquiries, the records move cleanly and the machinery does not. Each pipeline stage in Dropbox Sign needs an equivalent in Lawmatics, and stage names seldom line up. Open leads are loaded at the matching stage so that follow-up carries on. Closed and lost leads come across with their outcome, because conversion reporting depends on them. Sources and referrers are put into one list first.
Forms, email templates, sequences and automations are rebuilt by hand. It is worth doing on purpose: most firms find a sequence still running that nobody remembers setting up. Web forms and booking links on the firm’s site are repointed at cutover, and a test enquiry is put through each one. Consent and unsubscribe records move with the contacts and are checked separately, since a mistake there means emailing people who opted out.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Dropbox Sign 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 Dropbox Sign is kept running until the checks on Lawmatics are finished.
Where the data is now
Leaving Dropbox Sign
What a firm has in Dropbox Sign is a pile of executed documents and the proof of how each was signed. The work is getting every completed request out with its audit trail, matching each one to a client and matter, and filing it where the firm keeps its documents. Templates are rebuilt in the new signing tool.
The audit trail travels attached
Each completed request has an audit trail that timestamps events from submission to final signature and includes a hash of the PDF. By default it is appended to the signed document. Team plans can have it returned as a separate file. Either way it is kept with the document, since it is the record of how the signing happened.
Bulk download needs the API
In the web app, documents are downloaded one signature request at a time. Dropbox’s own guidance for downloading everything is to list every request through the API and fetch the files for each. On Premium team plans, cloud sync can instead copy all the team’s documents to a folder in Dropbox, Google Drive, OneDrive or Box.
Nothing says which matter
A signature request has a title, signers and dates. It has no matter number unless someone typed one into the title. Matching thousands of signed PDFs to matters is done from the signer’s email address, the title and the date, and the ones that cannot be matched are listed for the firm.
Requests still out for signature
A request that is waiting on a signer at cutover cannot be handed to another signing service half signed. It is either chased to completion in the old account or cancelled and sent again from the new tool. The list of open requests is drawn up well ahead of cutover so there is time to chase them.
Templates and embedded signing
Templates hold the field positions and signer roles for documents the firm sends often. Each is rebuilt in the new signing tool, unless the analysis finds a format both products accept. If the practice system or website calls the Dropbox Sign API to send documents, that connection is replaced as well.
Where it is going
Arriving in Lawmatics
Lawmatics takes matters, contacts and companies from CSV files, and its API accepts notes, tasks, appointments, files, time entries and invoices. It is an intake and client relationship system, so a firm arriving from full practice management has to decide what it is for. People and matters load well. There is no general ledger, and years of billing history have no natural home.
Contacts and matters load separately
The import expects two spreadsheets: one for contacts or companies with no case, such as referrers and other lawyers, and one for matters. A matter import creates the matter and its primary contact together. Every matter has exactly one primary contact, so joint clients are loaded as one primary and one relationship.
Set up before loading
Owner, stage, practice area, source and campaign are matched by name. A value on the spreadsheet that does not match one in Lawmatics exactly creates a new one, which is how a firm ends up with two spellings of the same practice area. Users, pipelines, practice areas and marketing sources are set up first, and custom fields must exist before data is loaded into them.
Statuses and matter numbers
Each imported matter must be PNC (potential new client), Hired or Lost, with open and closed handled as sub-statuses the firm creates. The case number is a system field assigned by an auto-numbering pattern and cannot be edited by hand afterwards. Whether old matter numbers can be loaded into it, or belong in a custom field, is tested in the trial load.
Duplicates are matched by email
With Match Contacts by Email switched on, a contact whose email already exists is skipped or updated, never doubled. Names and phone numbers are not checked. Matters are not deduplicated at all, so two rows with one email create two matters on one contact. Clean-up therefore happens in the spreadsheet, and automations are switched off for every load.
What has no place
There is no general ledger. The Time & Billing module holds time entries, expenses, invoices and a trust account with a running balance per matter, and past invoices are entered as already sent and then marked paid. A firm that needs its full accounting history keeps the old system read only or carries the books in an accounting package.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Lawmatics on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Dropbox Sign holds and how it is organised, then agree with you where each kind of record will sit in Lawmatics. 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 Lawmatics and checked against Dropbox Sign: 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 Dropbox Sign, a final pass over a weekend picks up what changed since the trial. Dropbox Sign 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 Dropbox Sign 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 Dropbox Sign holds
What is in it, how its records link, and where each piece would sit in Lawmatics. 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 Lawmatics
Loaded data is not yet a working system. This is what NewLaw sets up in Lawmatics, beyond the migration, so that people can work in it from the first day.
In Lawmatics the design comes before the data. The pipeline stages, practice areas, custom fields and relationship types decide what the import can hold, and the forms and automations decide what the firm’s intake looks like from the first day. If a practice system sits behind it, the field mapping between the two is part of the same job.
Set-up decisions in Lawmatics
- Pipelines and stages for intake and for open matters
- Practice areas, sub-statuses, relationship types and the matter numbering pattern
- Custom fields on matters, contacts and companies
- Intake forms, booking links and e-signature document templates
- Follow-up automations, with marketing sources and campaigns
- Mail and calendar sync, user roles and practice system integration
Questions
Dropbox Sign to Lawmatics: what firms ask
Can we still rely on documents signed in Dropbox Sign after we stop using it?
A completed PDF is a file the firm holds, and it stays readable without the account. What supports it later is the audit trail, which records the signing events and a hash of the document. That is why each document is exported with its trail attached or beside it, and both are filed against the matter.
Is this the same as HelloSign?
It is. HelloSign, HelloSign API and HelloFax were renamed Dropbox Sign, Dropbox Sign API and Dropbox Fax, and the old web address now leads to the Dropbox Sign site. Documents signed under the old name sit in the same account and are exported in the same way.
Can the signed documents go straight into our practice system?
They can be filed there if each one can be tied to a matter. Where the destination stores documents against matters, the signed PDFs are loaded into a signed-documents folder on each. If it does not hold documents at all, they go to the firm’s document store and the matter links to that folder.
Do documents from Dropbox Sign keep their folders and dates in Lawmatics?
In part. Files and folders on each matter, added by upload or API, not by the spreadsheet import. The structure in Dropbox Sign is mapped to what Lawmatics offers and you see the mapping before the load. File dates are carried.
Does everything in Dropbox Sign have a place in Lawmatics?
On paper, yes: each kind of record Dropbox Sign holds has a place in Lawmatics. 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 Dropbox Sign data is loaded into Lawmatics?
Documents, 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 Dropbox Sign and into Lawmatics
Other destinations from Dropbox Sign
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.
Dropbox Sign and Lawmatics are the names and marks of their owners, used here only to identify the two systems.
Moving from Dropbox Sign to Lawmatics?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.