My whole list, mirrored
onto a backup server.
My email list is the most valuable asset I own, so I never trust it to a single server. When someone registers on one of my forms, I add them to my main autoresponder, but I always want a backup. So I keep a second autoresponder where the same person also gets added, just in case something bad happens with the first one. I used to add them to the second server by hand, which wasted a lot of time. Now this automation syncs contacts between both servers in the right list, and it keeps every tag, every point, and every segment in step, so the backup is always a perfect mirror, set to send the day I need it.
Your list is your most valuable asset, and most people keep only one copy of it.
Your contacts are the part of the business you can least afford to lose. Yet most people keep their whole list on a single autoresponder, with no backup, and never think about it until the day that server locks them out or goes down. Building the list again from scratch is often impossible. The fix is to keep a full copy on a second server and let an automation keep the two in step, contact for contact, tag for tag. Here is who it is for, what goes wrong without it, how it works, and what you get back.
Who it’s for
Anyone whose business runs on an email list, creators, coaches, founders, and store owners who would be in real trouble if their autoresponder vanished overnight. It works even if you are not technical, because once it is set up, every new contact and every tag is mirrored to the backup with no effort from you.
What goes wrong
Without it, your whole business sits on one server you do not control. An account gets suspended, a server goes down, or a billing glitch locks you out, and your list is gone. The danger is not that you are careless. It is that one company holds your most valuable asset and you have no second copy to fall back on.
How the machine works
When someone signs up, the automation adds them to both servers in the same list. As they get tagged a buyer, awarded points, or sorted into segments on the first server, the same changes land on the second. You add contacts to nothing by hand. The backup server mirrors the main one on its own.
What you get back
A full, living backup of your list that is always current, plus the few minutes per signup you used to spend copying people over by hand. The day the first server ever fails, the backup can send and is already segmented, so you lose no contacts and no time.
I had my whole list on one server, and that quietly scared me.
For a long time my entire email list lived on a single autoresponder. It is the most valuable asset I own, the thing the whole business depends on, and it sat on one server controlled by one company. Every time I read about someone getting their account suspended overnight, or a platform going down, I felt that quiet fear in my stomach. If that server ever locked me out, I would lose years of work in an instant, and rebuilding a list from nothing is close to impossible.
So I decided I always wanted a backup. The idea was simple. When someone registers on one of my forms, I add them to my main autoresponder, but I also want the same person added to a second autoresponder, just in case something bad ever happens with the first one. The trouble was that doing it by hand was painfully slow. Every new contact meant logging into the second server and adding them again, which wasted time I did not have and which I would inevitably forget to do.
So I built an automation that syncs contacts between my servers. When a new person signs up, it adds them to both servers in the appropriate list, automatically, with no copying by hand. It also keeps the contact up to date as they get tagged, so the second server is never a stale snapshot. It is a living mirror of the first.
The part that makes this genuinely valuable is the tags. When someone buys a product and gets tagged as a buyer on autoresponder one, I make sure they are tagged as a buyer on autoresponder two as well. When they are awarded points or pick up a new tag that tells me more about their behaviour, that is reflected on the other server too. If the second autoresponder allows it, I move the person straight into a specific segment, so the backup is not just a list of emails, it can run high converting campaigns the day I need it.
The numbers here are intentionally modest and easy to check. Adding a new contact to the second server by hand only took a few minutes, but multiply that across every signup and it adds up fast, plus the times I simply forgot. Save a few minutes per signup and across a busy month that is hours back, every month. On top of that, the real payoff is a full backup of my most valuable asset, duplicated and kept current, that I never have to rebuild. Over three to five years, that is peace of mind that compounds quietly in the background.
Proof point: I have broken down how I run my business on autopilot and the income streams behind it on YouTube, in my 28 income streams breakdown and a real look at the daily work in a day in my life, so the conservative numbers on this page are checkable.
Three moves that keep a perfect backup of your list at all times
What made this work was treating the backup as a living copy, not a file you export once and forget. There is the contact, getting the right person into both servers, and there is the context, the tags, points and segments that tell you who they are. Most people, if they back up at all, copy the contacts and lose the context. The framework here keeps both servers identical, so the backup is always one you could actually use.
Add every new signup to both servers at once
The whole loop starts the moment someone registers on a form. Instead of adding them only to your main autoresponder, the automation adds them to the backup server too, in the matching list. This sounds obvious, and that is the point. The two lists never drift apart because every single new contact lands on both at the same instant. Without this, the backup falls behind a little more with every signup until it is useless. Get this right and the backup grows in perfect step with the main list, with no copying by hand and nothing for you to remember.
Keep every tag and point in step across both
A list of names is not enough. The value is in the tags, the buyer flags, the points, and the behaviour that tells you who each person is. So when a contact gets tagged a buyer on the first server, the automation puts the same tag on the second. When they earn points or pick up a tag about how they behave, that is reflected on the backup too. This is the move most backups miss. Because the context travels with the contact, the second server is never a flat list of emails. It is a true mirror you could actually run a campaign from.
Sort each contact into the right segment on the backup
The last move turns the backup from safe storage into something useful on day one. Where the second autoresponder allows it, the automation drops each person straight into the matching segment, buyers with buyers, warm leads with warm leads. So the backup is not just current, it is already organised the way you would want it for a campaign. The day you ever have to switch to it, you are not staring at a raw list wondering who is who. You open it, the segments are there, and you can run a high converting campaign immediately.
Once those three moves are in place, your backup stops being a stale export and starts behaving like a second live copy of your business. The signups keep both lists in step. The tags carry the context across. The segments keep the backup set to send. Your most valuable asset now lives in two places at once, kept identical without you lifting a finger.
Before the system
- My whole list living on a single server I did not control
- A quiet fear that one suspension would wipe out years of work
- Adding each new contact to the second server by hand
- A backup that was always out of date, if it existed at all
- No tags or segments on the backup, just a flat list of emails
After the system
- A full copy of my list living on two servers at once
- Every new signup added to both servers automatically
- Buyer tags and points kept identical across both
- Each contact sorted into the matching segment on the backup
- A backup I can send to today, with nothing to rebuild
Prompt 1: map your lists and tags across both servers
Before you sync anything, you need a clear picture of what should match across the two servers. The biggest mistake is syncing contacts but letting lists and tag names drift apart. Use this prompt to map your lists, tags, and points so both servers speak the same language.
List and tag mapping planner
Act as an email systems advisor. I keep my contacts on a main autoresponder and want a second autoresponder to hold a full, living backup of the same list. How my list is set up today: [describe your main lists, the tags you use, any points system, and how people sign up]. Map out a clear plan: which lists on server one should match which lists on server two, how to name tags so they line up across both, which buyer flags and points need to travel, and where the two are likely to drift apart. For each pairing, one line on what to keep identical and why it matters if I ever have to use the backup.
The output is a mapping you set up once. Get this right and both servers always speak the same language, so the backup is a true mirror rather than a confusing copy.
Prompt 2: design the signup sync between both servers
With the mapping clear, the first job is making sure every new signup lands on both servers in the right list. Use this prompt to design that flow so no contact is ever added to one server and forgotten on the other.
Signup sync designer
Act as an automation analyst. I want every new signup on my forms added to my main autoresponder and to a backup autoresponder at the same time, each in the matching list. Where people sign up and which lists they should join: [describe your forms and the lists each one feeds]. Design the flow: how a signup triggers an add on both servers, how to place the person in the right list on each, what to do if one server is briefly unreachable, and how to confirm the contact really landed on both. For each step, one line on how it stops the two lists from drifting apart.
Save the output as your signup blueprint. This is the move that keeps both lists growing in perfect step, so the backup never quietly falls behind the main one.
The 3-minute overview of how this works
Before the build steps, watch this short overview. It’s the exact video from the Automations Made Easy page, and it walks through the mechanics behind machines like this one. 1,000+ students have used these mechanics to save two hours a day, with zero coding.
Want to learn the mechanics behind admin automations like this?
I teach the same mechanics that power this contact sync inside Automations Made Easy. 1,000+ students have used these mechanics to save two hours a day and build little machines that quietly protect the boring but vital parts of the business. No coding required.
Week one: both servers synced, your backup already current.
Most people put off backing up their list because it feels like a big technical project. That is exactly why this machine matters. A contact sync is meant to feel like a small setup you do once, not a chore you maintain. In week one you map your lists and tags, wire new signups to both servers, and watch the backup catch up to the main list, so the quiet fear of losing everything starts to fade right away.
Week one looks like this. On Monday you map which lists and tags on server one should match server two, so both speak the same language. Then you wire new signups to land on both servers in the right list, and confirm a test contact really arrives on each. By midweek you set the tags and points to mirror across, so a buyer on one becomes a buyer on the other. By the end of the week your backup holds the same contacts, the same tags, and the same segments as your main list. A full living copy of your most valuable asset, already current.
The point of the first week is not the minutes saved. The point is to confirm the backup is a true mirror, the contacts match, the tags carry across, and the segments are in place. Once that is locked, every signup and every tag after it keeps both servers identical on its own, with no effort from you.
From there the maths is simple and conservative. Adding a contact to the second server by hand took a few minutes each time, plus the signups I forgot entirely. Save a few minutes per signup and across a busy month that is hours back, every month, more than twenty hours over a year. On top of the time, you hold a full backup of your most valuable asset that stays current on its own. Over three to five years, that compounds into a business that can survive losing a server without losing a single contact.
All of this runs while you work on something else, travel, or sleep. Someone signs up, gets tagged, earns points, and both servers stay identical without you touching anything. No copying contacts by hand, no stale backup, no quiet fear that one suspension ends the business. Your list lives in two places at once, kept current, set to send.
Prompt 3: keep tags and points in sync over time
Adding contacts is only half the job. The backup is only useful if the tags and points stay current too. Use this prompt to design how buyer flags, points, and behaviour tags are mirrored from one server to the other as people change.
Tag sync designer
Act as a marketing automation advisor. I want changes on my main autoresponder mirrored onto my backup autoresponder, so the backup always reflects who each contact really is. What changes I track on a contact: [list your buyer tags, any points or scoring, and the behaviour tags you apply]. Design the sync: how a new tag or point on server one is reflected on server two, how often it should run, what to do about tags removed or changed, and how to avoid duplicates or conflicts. For each tag type, one line on why keeping it current matters if I ever have to send from the backup.
The output is the plan for keeping context alive on the backup. Run this and the second server stays a true mirror, not a flat list, so it is good to use the moment you need it.
Prompt 4: build segments on the backup, set to send
The point of all this is that the backup can run a campaign on day one. To get there, each contact should drop into the right segment on the second server. Use this prompt to design those segments so the backup is organised, not just current.
Backup segment planner
Act as an email campaign strategist. My backup autoresponder holds a full copy of my list with the same tags and points. I want it already organised into segments, so I could run a high converting campaign from it immediately. The segments I care about: [describe your key segments, for example buyers, warm leads, new signups, by tag or behaviour]. Design the segments on the backup: which tags and points define each one, how a contact moves between them as they change, and which segments are most valuable to have ready in an emergency. For each segment, one line on the campaign I could send to it on day one.
The output is a backup you can use, not just one you store. Settle it once and the day you ever switch servers, the segments are already there and you can send right away.
The exact build, step by step
Map your lists and tags across both servers
Start with the mapping, because that is what keeps the two servers speaking the same language. You decide which list on the main autoresponder matches which list on the backup, and you line up the tag names, the buyer flags, and any points system so they mean the same thing on both. You do not need anything clever here, just a clear pairing. This is the foundation the whole sync rests on, because if the lists and tags do not line up, the backup becomes a confusing copy instead of a true mirror you can actually use.
Add each new signup to both servers automatically
The mapping is in place, and now the automation does the part you used to do by hand. The moment someone registers on a form, they are added to your main autoresponder and to the backup server at the same time, each in the matching list. You never log into the second server to copy anyone over, and you never forget. Because every signup lands on both at once, the two lists grow in perfect step and never drift apart. This is the move that turns a stale, half built backup into a living copy that keeps pace with the main one.
Mirror the buyer tag when someone purchases
A contact is more than a name, so the next move keeps the most important context in sync. When someone buys a product and gets tagged as a buyer on the first server, the automation puts the same buyer tag on the second. This matters because buyers are the people you treat differently, and a backup that does not know who bought is a backup you cannot really sell from. Now both servers agree on who your customers are, so the backup is not just a list of emails. It knows the difference between a buyer and a fresh lead, exactly like the main one.
Reflect new points and behaviour tags across both
Buyers are not the only thing that changes. As people open emails, click offers, and earn points, those signals build up on the first server, and this step carries them to the second. When a contact is awarded points or picks up a new tag that tells you more about their behaviour, that is reflected on the backup too. So the second server does not just know who bought, it knows who is warm, who is active, and who is going quiet. The backup stays a true picture of your audience, not a snapshot frozen at the moment they signed up.
Drop each contact into the matching segment
A current backup is good, but an organised one is better. Where the second autoresponder allows it, this step drops each person straight into the matching segment, buyers with buyers, warm leads with warm leads, new signups with new signups. You do no sorting by hand, the tags and points decide where each contact belongs. Now the backup is not just a copy of your list, it is a copy already arranged the way you would want it for a campaign. This is the step that makes the backup useful on day one, not just safe in storage.
Keep the backup ready for the day you need it
Final piece. Because every signup, every tag, and every segment is kept in step, the backup is always a perfect mirror of your main list. If the first server is ever suspended, goes down, or locks you out, you do not lose your most valuable asset and you do not start over. You open the second server, the contacts are all there, the tags are in place, and the segments are ready. You can run a high converting campaign that same day. This is the part that compounds, peace of mind that grows quietly while the machine keeps both servers identical for you.
Lists mapped
You line up which lists and tags on the main server match the backup, so both speak the same language.
Signup synced
The moment someone registers, they are added to both servers automatically, each in the right list.
Tags mirrored
Buyer flags, points, and behaviour tags on the first server are reflected on the backup as they change.
Backup ready
Each contact sits in the right segment, so the backup is current and set to send the day you need it.
Build this admin engine inside the same playbook 1,000+ students use
Automations Made Easy teaches the mechanics behind quiet, vital bots like this one. Step by step, no code, plain English. Save two hours a day and own little machines that protect your most valuable assets while you do the work you enjoy.
The six months after I switched it on
Here is the shape of the first six months after I turned the contact sync on. The line tracks the time and the safety value I got back as I replaced the by hand copying with a backup that keeps itself current, which is exactly how this machine pays off in practice.
Monthly value from a backup that keeps itself current
Three things matter on this chart. The value climbs steadily as I stop copying contacts by hand and stop worrying about losing the list, not in a spike. The savings come from time reclaimed and the risk I no longer carry. And every single one of those months happens while the automation keeps both servers identical for me, without being asked.
What other students built
I teach the simple skills behind machines like this in Automations Made Easy. Students who built their own version sent back what changed in their first month.
“I always knew I should back up my list and never got round to it. Now every signup lands on both servers and the backup is always current. If one ever goes down, I am not finished.”
“The clever part is the tags. My backup knows who my buyers are, not just their emails. I could run a sale from the second server tomorrow and it would land on the right people.”
“I used to add new contacts to my second autoresponder by hand and forget half the time. Now it happens on its own. The few minutes per signup add up to hours I got back every month.”
“Knowing the first week was just mapping lists and tags kept me patient. By the end of it my backup mirrored everything, segments included. The quiet fear of losing my list is gone.”
What’s inside Automations Made Easy
AME isn’t a library of pre-built automations. Every business is slightly different. What’s reusable across all of them is the underlying mechanics: how to set up little machines that listen, write, and follow up while you sleep, and how to wire the pieces together without writing code.
The program walks you through six modules: The Right Tools (the cost-effective, no-code stack I actually use), Task Selection Mastery (which automations are worth building first), Design Secrets (mapping an automation before you build it), Zero to Hero (complete beginner to confident automator), Real-World Application (we build a full automation together, end to end), and Monetization Mastery (turn the skill into a side-business).
It also includes done-for-you templates you import in two clicks, over-the-shoulder training videos, and the same playbook 1,000+ students have used to save two hours a day. No coding required. If you can copy and paste, you can build this.
Synchronizing contacts between servers: common questions
Pulled from what readers and Automations Made Easy students ask most.
Do I need to be a developer to set this up?
No. Mapping your lists and tags is a one time setup, and the sync that adds contacts and mirrors tags is built by following steps. You decide what should match across the two servers, then the automation handles the copying. The skills you need are keeping the lists and tags lined up clearly, which is exactly what Automations Made Easy teaches.
Why keep a backup on a second server at all?
Because your list is the most valuable asset you own, and most people keep it in one place they do not control. An account can be suspended, a server can go down, or a billing glitch can lock you out, and rebuilding a list from nothing is close to impossible. A second server that mirrors the first means one bad day never ends your business.
Does the backup stay current, or is it a one time copy?
It stays current. Every new signup is added to both servers, and as a contact is tagged a buyer, awarded points, or sorted into a segment on the first server, the same changes land on the second. The backup is a living mirror, not a snapshot you export once and forget, so it always reflects who each contact really is.
Will the tags and segments really match across both servers?
Yes, as long as you line up the list and tag names once at setup. After that, a buyer on server one becomes a buyer on server two, points and behaviour tags travel across, and where the second autoresponder allows it each contact drops into the matching segment. That is what makes the backup good to send from rather than just a flat list of emails.
How much time does this really save?
Conservatively, it saves a few minutes per signup that used to be manual, plus the signups you would have forgotten to copy at all. Across a busy month that adds up to hours back. The bigger payoff is harder to put a number on, a full backup of your most valuable asset that you never have to rebuild and can send from the day you need it.
More Money Makers like this one
Built from the same handful of mechanics. Each one captures, converts, or earns money that would have walked out the door.
Build this contact sync yourself, or learn the mechanics inside Automations Made Easy.
If you want to learn the mechanics behind admin automations like this and build your own at home, Automations Made Easy is the playbook. Step by step, no code, plain English. If you want to talk through how to map your lists, wire your signups to both servers, and keep your tags in sync first, I take a small number of consulting clients each month.
€497 one-time · Lifetime access · 1,000+ students
