REsimpli drip campaigns stopped after 6.0? Here is how to restart them

If your follow-up went quiet after September 12, this is why. REsimpli moved every 5.0 drip campaign into the new Automations feature and switched it off during the upgrade. Nothing was deleted, but nothing restarts on its own either. These are the steps from REsimpli’s own help center.

1. 1

   Open the new Automation and check it

   Variable fields from 5.0 migrate to their 6.0 fields automatically, but open each message and check its variables display correctly before you enrol anyone.

2. 2

   Filter leads by Legacy Drip Campaign (pre-6.0)

   In your lead filters, choose Legacy Drip Campaign (pre-6.0), then the specific campaign, to see every lead that was on it.

3. 3

   Add those leads to the matching Automation

   Select the leads and add them with Bulk Actions. REsimpli’s automation article says bulk-adding works on Manual Assignment automations.

4. 4

   Pace the re-enrolment

   The bulk limit is 100 records a day, shared across the whole account, so put your hottest leads in first.

5. 5

   Expect a restart from step one

   Leads begin the automation again from the first step. Picking up mid-sequence is not possible, and task cards reset.

How long will re-enrolling take?

At 100 records a day across the whole account, the arithmetic decides your schedule. Type your own number:

Leads to re-enrol

20 days of bulk adds at 100 a day

Will leads pick up where they left off?

No. REsimpli says leads restart the automation from the beginning and task cards reset. For long sequences that means some sellers will receive an opener they already got months ago. Before you enrol a group that was deep into a drip, consider editing the first steps of that automation, or enrolling those leads into a shorter re-engagement automation instead.

Do bulk status changes or imports restart anything?

Not on their own. REsimpli’s automation article says a status-change trigger fires when a user or another automation changes the status, not on bulk status changes or imports, and changes made through the Open API do not fire automations at launch. If you were counting on a bulk status change to kick a sequence back on, it will not.

When does it make sense to rebuild follow-up elsewhere?

If you are restarting every sequence from step one anyway, you are close to rebuilding them. Some teams use that moment to ask whether their follow-up should live in REsimpli at all. If you are weighing that, the 6.0 guide covers the rest of what changed, and the migration page shows how automations are inventoried and rebuilt as HubSpot workflows, switched on only after you approve each one.