Data migration route
Mailchimp to SimpleLaw migration
Mailchimp is a cloud contacts and calendar tool, and SimpleLaw is a cloud practice management system. This is a narrow move: the records Mailchimp holds are matched to the people and matters in SimpleLaw.
MailchimpCloud- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Intake: Carried across
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
SimpleLawCloud- 5 carried
- 2 mapped
- 1 to confirm
What moves
What moves from Mailchimp to SimpleLaw
Each row is a kind of record Mailchimp holds, whether SimpleLaw has a place for it, and what is planned. On this route five kinds of record carry across, two kinds need mapping and one kind is confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldAudience contacts with fields, tags and groups, each with a subscription status. | Has a placeAs leads, clients or other contacts in the CRM. | Carried across |
| DocumentsFiles stored in or linked from the system | Held in partImages and files stored in the content studio. | Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partSent campaigns are kept as HTML and text. These are bulk emails, not correspondence. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held in partNotes added on a contact’s profile are included in contact exports. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | Held in partAppointments booked through Mailchimp can be exported as CSV. | Has a place | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldAudience fields are defined separately for each audience. | Has a place | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldEmail templates, exported as HTML files. | Has a place in partTemplates are rebuilt using SimpleLaw’s own automation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partSignup forms add contacts to an audience. | Has a placeLeads and intake forms. | Carried across |
What the plans mean
- Carried across
- SimpleLaw has a place for this kind of record. It is loaded there and checked against Mailchimp.
- Carried with mapping
- SimpleLaw holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
- Confirmed in the analysis
- We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.
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 Mailchimp 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 SimpleLaw, 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 SimpleLaw 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 Mailchimp 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 Mailchimp is kept running until the checks on SimpleLaw are finished.
Where the data is now
Leaving Mailchimp
Mailchimp lets an account owner export everything as one zip file: audiences, sent emails, templates, reports and the image gallery. The contacts are the part that matters, and specifically their status. Who subscribed, who unsubscribed and when they confirmed is the firm’s consent record, and it has to arrive in the new system intact.
Four files per audience
An audience export is a zip of separate CSV files for subscribed, unsubscribed, non-subscribed and cleaned contacts. Loading only the subscribed file is the common mistake. The unsubscribed and cleaned files are loaded too, as suppressed addresses, so the new system knows never to email them.
Opt-in evidence is in columns
Each row carries OPTIN_TIME, CONFIRM_TIME and the IP addresses recorded when the person signed up and confirmed. If the firm is ever asked how it came to be emailing someone, those columns are the answer. They are kept as fields on the contact where the destination allows, and the original export files are archived either way.
Tags, groups and segments
Firms sort their lists three different ways in Mailchimp. Tags and groups are stored on the contact. A segment is a saved filter, so it exports only as the list of people who match it today. Each one still in use is mapped to a category, list or tag in the destination.
Reports cannot be re-imported
The account export includes open and click data for each email, down to individual contacts. Mailchimp notes that everything in the export can be re-imported except email and SMS reports, and few other systems have a place for them. The reports are kept as files for reference, and engagement history starts fresh.
Several audiences, same people
Some accounts have a separate audience for each newsletter, with the same person in several and unsubscribed from only one. Mailchimp’s own advice is to keep one primary audience. The audiences are merged before loading, and an unsubscribe in any of them is honoured unless the firm decides otherwise list by list.
Where it is going
Arriving in SimpleLaw
Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.
Lead, client or contact
A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.
Billing type on each matter
Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.
Storage chosen before loading
If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.
Custom fields named for templates
Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.
Portal access client by client
The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in SimpleLaw on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Mailchimp holds and how it is organised, then agree with you where each kind of record will sit in SimpleLaw. 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 SimpleLaw and checked against Mailchimp: 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 Mailchimp, a final pass over a weekend picks up what changed since the trial. Mailchimp 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 Mailchimp 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 Mailchimp holds
What is in it, how its records link, and where each piece would sit in SimpleLaw. 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 SimpleLaw
Loaded data is not yet a working system. This is what NewLaw sets up in SimpleLaw, beyond the migration, so that people can work in it from the first day.
The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.
Set-up decisions in SimpleLaw
- Labels for documents, activities, expenses and contact IDs
- Custom fields and intake forms for each practice area
- Document templates and the attorney-client agreement
- Workflows for case types that follow a standard process
- User permission sets and client portal visibility
- QuickBooks connection and the online payment processor
Questions
Mailchimp to SimpleLaw: what firms ask
Do unsubscribes carry over?
They do if the unsubscribed and cleaned files are loaded along with the subscribed one, which is why all the files are in scope. Each address keeps its status in the destination. Before the first send from the new system, a test confirms that a known unsubscribed address is excluded from the mailing.
Can our old newsletters be kept?
Yes, as files. The account export includes a CSV of regular emails and a folder with the HTML and plain text of each one, and templates come out as HTML. They can be stored in the firm’s document system. Rebuilding a template in a new email tool is a separate design job.
Do documents from Mailchimp keep their folders and dates in SimpleLaw?
SimpleLaw stores documents. Uploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. 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 Mailchimp have a place in SimpleLaw?
Most of it does on paper. Emails could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in SimpleLaw is kept as a readable archive, and you see which before the move.
What has to be decided before Mailchimp data is loaded into SimpleLaw?
Custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from Mailchimp and into SimpleLaw
Other destinations from Mailchimp
Other systems that move into SimpleLaw
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.
Mailchimp and SimpleLaw are the names and marks of their owners, used here only to identify the two systems.
Moving from Mailchimp to SimpleLaw?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.