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

Data migration route

Mailchimp to Neos migration

Mailchimp is a cloud contacts and calendar tool, and Neos 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 Neos.

FromMailchimpCloud
  1. Contacts: Carried across
  2. Documents: Carried across
  3. Notes: Carried across
  4. Calendar: Carried across
  5. Intake: Carried across
  6. Emails: Carried with mapping
  7. Custom fields: Carried with mapping
  8. Templates: Carried with mapping
ToNeosCloud
  • 5 carried
  • 3 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Mailchimp to Neos

Each row is a kind of record Mailchimp holds, whether Neos has a place for it, and what is planned. On this route five kinds of record carry across and three kinds need mapping.

Records in Mailchimp and their place in Neos
RecordIn MailchimpIn NeosWhat is planned
ContactsClients, other parties and referrersHeldAudience contacts with fields, tags and groups, each with a subscription status.Has a placeParties, providers and case contacts. Contacts can be imported from CSV.Carried across
DocumentsFiles stored in or linked from the systemHeld in partImages and files stored in the content studio.Has a placeCase Docs tab, organised in sub-tabs.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 partEmails tagged to a case are held. Loading old mail is scoped in the analysis.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 placeCarried across
CalendarAppointments, court dates and deadlinesHeld in partAppointments booked through Mailchimp can be exported as CSV.Has a placeCase calendar entries.Carried across
Custom fieldsFields and record types the firm added itselfHeldAudience fields are defined separately for each audience.Has a placeUser-defined fields are created on the relevant tab first.Carried with mapping
TemplatesPrecedents, document templates and automationHeldEmail templates, exported as HTML files.Has a place in partTemplates are rebuilt for Neos document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partSignup forms add contacts to an audience.Has a placeIntakes tab. Simple intake imports from CSV are supported.Carried across

What the plans mean

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

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 Neos, 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 Neos 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 Neos are finished.

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

Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.

  1. Every figure needs a value code

    Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.

  2. Lists are set up first

    Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.

  3. Documents go to sub-tabs

    Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.

  4. Reminders split two ways

    Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.

  5. Assembly runs its own conversions

    Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.

More about moving into Neos

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Neos on this route, which makes it repeatable: a load can be run again until it is right. The maker of Neos says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Mailchimp and checking each trial against Mailchimp.

  1. Analysis

    We read what Mailchimp holds and how it is organised, then agree with you where each kind of record will sit in Neos. 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 Neos 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 toNeos

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

Setting up Neos

Loaded data is not yet a working system. The maker of Neos runs or arranges the set-up of its product, so this is what has to be decided and put in place in Neos, whoever does the work, before people rely on it from the first day.

Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.

Set-up decisions in Neos

  • Set case types, statuses and staff roles
  • Agree the value code list with accounts staff
  • Build checklists for each case type and stage
  • Create user-defined fields for data the tabs lack
  • Prepare document templates for the generation wizard
  • Connect Microsoft 365, QuickBooks and the phone system

Questions

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

Neos stores documents. Case Docs tab, organised in sub-tabs. 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 Neos?

On paper, yes: each kind of record Mailchimp holds has a place in Neos. 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 Mailchimp data is loaded into Neos?

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

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

Moving from Mailchimp to Neos?

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

We reply within one business day.