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

Data migration route

Mailchimp data to SQLite

Mailchimp is a cloud contacts and calendar tool, and SQLite is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what Mailchimp holds and keeps it readable and open to queries.

FromMailchimpCloud
  1. Contacts: Exported in full
  2. Notes: Exported in full
  3. Calendar: Exported in full
  4. Intake: Exported in full
  5. Documents: Exported with mapping
  6. Emails: Exported with mapping
  7. Custom fields: Exported with mapping
ToSQLiteFiles
  1. Templates: Kept as a readable archive
Readable archiveNo place in SQLite
  • 4 carried
  • 3 mapped
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Mailchimp to SQLite

Each row is a kind of record Mailchimp holds, whether SQLite has a place for it, and what is planned. On this route four kinds of record carry across, three kinds need mapping and one kind has no place in SQLite and is archived.

Records in Mailchimp and their place in SQLite
RecordIn MailchimpIn SQLiteWhat is planned
ContactsClients, other parties and referrersHeldAudience contacts with fields, tags and groups, each with a subscription status.Has a placeContacts and their roles on matters as linked tables.Exported in full
DocumentsFiles stored in or linked from the systemHeld in partImages and files stored in the content studio.Has a place in partListed in a table; the files themselves stay in folders beside the database.Exported with mapping
EmailsEmails saved to matters or to the storeHeld in partSent campaigns are kept as HTML and text. These are bulk emails, not correspondence.Has a place in partAs message files in folders, indexed in a table.Exported with mapping
NotesFile notes, matter notes and contact notesHeld in partNotes added on a contact’s profile are included in contact exports.Has a placeA notes table linked to matters.Exported in full
CalendarAppointments, court dates and deadlinesHeld in partAppointments booked through Mailchimp can be exported as CSV.Has a placeA table of dated entries, with no calendar view.Exported in full
Custom fieldsFields and record types the firm added itselfHeldAudience fields are defined separately for each audience.Has a placeColumns added to the table they belonged to.Exported with mapping
TemplatesPrecedents, document templates and automationHeldEmail templates, exported as HTML files.No placePrecedent files are kept in folders, not in the database.Kept as a readable archive
IntakeLeads, enquiries, intake forms and pipelinesHeld in partSignup forms add contacts to an audience.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 Mailchimp.
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 Mailchimp 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

Not a new system. A complete copy the firm can query.

Writing Mailchimp out to SQLite is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Mailchimp as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

Mailchimp 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 Mailchimp will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

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.

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

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

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

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

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

More about moving off Mailchimp

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 Mailchimp holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Mailchimp 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 Mailchimp: record counts, totals where Mailchimp 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 Mailchimp, the export is run a final time and checked again. There is nothing to go live. Mailchimp 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 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

Step 1 of 5: Start with the route

Moving fromMailchimp
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 Mailchimp 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

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

Does the copy in SQLite hold documents from Mailchimp?

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

What happens to records SQLite has no place for?

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

Documents, emails 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

Mailchimp and SQLite are the names and marks of their owners, used here only to identify the two systems.

Moving from Mailchimp 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.