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

Data migration route

Mailchimp to Server drives migration

Mailchimp is a cloud contacts and calendar tool, and Server drives are plain files on equipment the firm controls. What moves is the files, plus a readable export of everything else the old system holds.

FromMailchimpCloud
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Notes: Carried with mapping
  4. Templates: Carried with mapping
ToServer drivesFiles
  1. Contacts: Kept as a readable archive
  2. Calendar: Kept as a readable archive
  3. Custom fields: Kept as a readable archive
  4. Intake: Kept as a readable archive
Readable archiveNo place in Server drives
  • 1 carried
  • 3 mapped
  • 4 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Mailchimp to Server drives

Each row is a kind of record Mailchimp holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping and four kinds have no place in Server drives and are archived.

Records in Mailchimp and their place in Server drives
RecordIn MailchimpIn Server drivesWhat is planned
ContactsClients, other parties and referrersHeldAudience contacts with fields, tags and groups, each with a subscription status.No placeCan be kept only as an exported spreadsheet.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeld in partImages and files stored in the content studio.Has a placeFiles in folders, named and dated during the load.Carried across
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 .msg or .eml files in each matter’s correspondence folder.Carried with mapping
NotesFile notes, matter notes and contact notesHeld in partNotes added on a contact’s profile are included in contact exports.Has a place in partAs a text or PDF file per matter, not as separate records.Carried with mapping
CalendarAppointments, court dates and deadlinesHeld in partAppointments booked through Mailchimp can be exported as CSV.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldAudience fields are defined separately for each audience.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationHeldEmail templates, exported as HTML files.Has a place in partPrecedents as Word files; merge fields tied to the old system stop working.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partSignup forms add contacts to an audience.No placeKept as a readable archive

What the plans mean

Carried across
Server drives has a place for this kind of record. It is loaded there and checked against Mailchimp.
Carried with mapping
Server drives 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
Server drives 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

An export the firm can open without the system.

Server drives hold files, and most of what Mailchimp holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used Mailchimp, by client or by year, with a short index file saying what is where.

Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in Server drives is limited before the export is copied in.

Mailchimp is hosted by its maker and Server drives sit 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

Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.

  1. Agree the tree and the names

    A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.

  2. Budget the path length

    Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.

  3. Dates have to be set deliberately

    A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.

  4. Emails become message files

    Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.

  5. Keep an index beside the files

    A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.

More about moving into Server drives

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Server drives on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Mailchimp holds and how it is organised, then agree with you where each kind of record will sit in Server drives. Anything with no place there stays behind or is archived, and you see which before the move.

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

  3. Trial load

    A trial is loaded into Server drives 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.

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

Step 1 of 5: Start with the route

Moving fromMailchimp
Moving toServer drives

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 Server drives. 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

Server drives are storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.

What is agreed and set up

  • Share and top-level folders for clients, precedents and administration
  • Security groups and folder permissions, with restricted matters separate
  • Drive letter mapped for every user at sign-in
  • Backup schedule and shadow copies for earlier versions
  • Written naming rule for client, matter and document names
  • Read-only area for closed matters and archived system exports

Questions

Mailchimp to Server drives: 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 Server drives?

Server drives store documents. Files in folders, named and dated during the load. 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.

What happens to records Server drives have no place for?

On this route that is contacts, calendar entries, custom fields and intake records. 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 data is loaded into Server drives?

Emails, notes 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.

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

Moving from Mailchimp to Server drives?

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

We reply within one business day.