Data migration route
Mailchimp to Gladiate migration
Mailchimp is a cloud contacts and calendar tool, and Gladiate is a cloud case management system for personal injury work. This is a narrow move: the records Mailchimp holds are matched to the people and matters in Gladiate.
MailchimpCloud- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Intake: Carried across
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
GladiateCloud- 4 carried
- 1 mapped
- 3 to confirm
What moves
What moves from Mailchimp to Gladiate
Each row is a kind of record Mailchimp holds, whether Gladiate has a place for it, and what is planned. On this route four kinds of record carry across, one kind needs mapping and three kinds are 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 placeClients, leads and referral sources. | Carried across |
| DocumentsFiles stored in or linked from the system | Held in partImages and files stored in the content studio. | Has a placeFiled to the firm’s folder structure. | 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. | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partAppointments booked through Mailchimp can be exported as CSV. | Has a placeEvents sync with Outlook and Google Calendar. | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldAudience fields are defined separately for each audience. | To be confirmed | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldEmail templates, exported as HTML files. | Has a place in partFirm templates are set up again in Gladiate. Old templates are not converted. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partSignup forms add contacts to an audience. | Has a placeLeads and client sign-up. | Carried across |
What the plans mean
- Carried across
- Gladiate has a place for this kind of record. It is loaded there and checked against Mailchimp.
- Carried with mapping
- Gladiate 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 Gladiate, 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 Gladiate 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 Gladiate 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 Gladiate
Gladiate is a destination for personal injury firms, and what it expects is injury data: a client, an incident, coverage, providers and a case status. Loading a firm into it means shaping the old system’s records into that pattern and preparing the templates, task plans and folder structure that the vendor’s onboarding asks each firm to supply.
Injury fields come first
Coverage, liability and medical details are what the product is designed to put in front of staff. In the old system they may be in custom fields, notes or a spreadsheet. They are pulled into columns during the analysis, so a loaded case shows its insurer and policy details and not an empty panel.
Templates and task plans
The vendor’s onboarding has each firm set up its own document templates, task plans, litigation deadlines and questionnaires. These are prepared from what the firm uses now. Merge fields in old templates are replaced with Gladiate’s, and task plans are written down stage by stage before anyone builds them.
A folder structure per case
Documents are filed in a folder structure the firm defines. The old system’s folders or categories are mapped to it once, and every case is loaded to the same pattern. Files with no clear category go to a holding folder on the case and are listed, not scattered.
What it may not hold
Time records, invoices and trust ledgers are not described on the vendor’s public pages. A firm that needs those carried over has it confirmed in the analysis. If there is no place for them, balances stay in the accounting package and the detailed history is kept in the old system, read only.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Gladiate 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 Gladiate. 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 Gladiate 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 Gladiate. 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 Gladiate
Loaded data is not yet a working system. This is what NewLaw sets up in Gladiate, beyond the migration, so that people can work in it from the first day.
Gladiate is delivered ready for injury work, so set-up is about making it the firm’s own. The vendor’s onboarding covers templates, task plans, folder structure, litigation deadlines and client questionnaires. Each of those is a decision the firm has to make, and it goes faster when current practice has been written down beforehand.
Set-up decisions in Gladiate
- Set up and test the firm’s document templates
- Write task plans for each stage of a case
- Agree one folder structure for case documents
- Enter litigation deadlines for the firm’s jurisdictions
- Prepare client questionnaires, surveys and scheduled case updates
- Connect Outlook or Google calendars for two-way sync
Questions
Mailchimp to Gladiate: 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 Gladiate?
Gladiate stores documents. Filed to the firm’s folder structure. 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 Gladiate?
Most of it does on paper. Emails, notes and custom fields 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 Gladiate is kept as a readable archive, and you see which before the move.
What has to be decided before Mailchimp data is loaded into Gladiate?
Templates are carried with mapping, so each mapping is agreed with you first. Emails, notes and custom fields 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 Gladiate
Other destinations from Mailchimp
Other systems that move into Gladiate
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 Gladiate are the names and marks of their owners, used here only to identify the two systems.
Moving from Mailchimp to Gladiate?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.