How to Migrate to Follow Up Boss Automation 2.0 Without Losing Your Triggers

This is the readable version of our video walkthrough.

A team upgrades to Follow Up Boss's new automation system, feels good about the migration, and three weeks later notices the buyer guide isn't going out anymore. Nothing broke. Nothing failed. The trigger that used to fire automatically simply isn't there anymore, and unless someone knew to check for it, the gap stays invisible until a lead falls through it.

That's the one detail in Automation 2.0 that matters more than any of the new features it ships with. Here's the full picture.

What Automation 2.0 Actually Is

In the old system, building a working sequence meant two separate steps: create an Action Plan (the emails, tasks, and stage changes in order), then build a matching Automation (the trigger, the condition, and which action plan to fire). Two tools, built separately, then linked together.

Automation 2.0 merges both into one workspace. You build the trigger and the sequence in the same place, at the same time. Once you upgrade, you can still view your old action plans, but you can no longer edit or create new ones the old way. Everything going forward lives inside Automations.

The Migration Detail That Catches Teams Off Guard

Follow Up Boss automatically migrates every existing action plan into the new system for you, into a folder labeled something like "migrated action plans." That part is genuinely useful and saves a full rebuild.

Here's the catch: every migrated action plan comes through with only a manual trigger. In the old system, a plan might have fired automatically off a tag, a stage change, or an inquiry. After migration, that automatic trigger is gone. The plan still exists and still works, but only if someone manually applies it to a lead.

If your buyer guide used to go out the moment a lead got tagged "buyer," it won't anymore, not until you go back into that migrated automation and rebuild the trigger yourself.

Before you migrate, document what's already firing automatically. A screenshot of each automation's trigger and condition, or a quick spreadsheet noting which tag or stage change sets off which plan, is enough. Without it, you're rebuilding a system you didn't fully remember you had, from memory, under time pressure, after leads have already started slipping.

What's Actually New and Worth Using

Once the migration housekeeping is handled, several genuine upgrades are worth building into your setup.

• Time delays now go down to the minute, not just the day. A delay can be five minutes, two hours, or a full day, which closes the gap that used to require a third-party texting or drip tool.
• A new appointment trigger. Automations can fire based on an appointment being created, a set time before or after it, or a specific appointment outcome.
• Recipient and delivery preferences on every email step. Send to the primary contact only, or to everyone connected to that record. Delivery can go out immediately, only within business hours, or on a fully custom schedule.
• A true drag-and-drop builder, with the time delay itself as a draggable element between steps.
• Pause and resume, at the step or whole-automation level, plus the ability to run a specific automation against a lead on demand.

What Stays the Same

Folders are still here, which matters, since folder organization existed for action plans in the old system but not for standalone automations. Conditions still work the way they did (agent assignment, phone number quality, whatever filter you were already using). And the manual-apply option itself isn't new, it's the same "add this action plan to a lead" button that existed before, just repositioned as the fallback every migrated plan now defaults to.

The One Filter to Run This Through

The instinct after a migration like this is to rebuild everything at once. Don't. Go through each migrated automation and ask one question: did this used to fire on its own, and does it still need to? If yes, rebuild the trigger before anything else. Everything new is worth exploring after the plans you already depend on are confirmed to be firing the way they used to.

Where This Fits Into the Bigger Picture

Automation 2.0 changes how sequences get built and triggered. It doesn't change whether your team knows which sequences exist, which ones are still doing their job after a migration, or who's responsible for checking. That's the layer above the tool, and it's the difference between a migration that quietly breaks follow-up and one that improves it.

If you're mid-migration or planning one and want a second set of eyes on what did and didn't carry over, that's exactly the kind of audit built to surface it.