convertkit Migration to visual automation: migrate to the new visual automation feature launched in August

Migration to visual automation: migrate to the new

visual automation feature launched in August



In this article, we will show you how to migrate to the new visual automation feature launched in August 2017.

Before you start, you should take an inventory of the entire automation configuration. This is a perfect time to clean up old forms, sequences and automation rules that are no longer in use. It does not make sense to migrate more than necessary!
Then keep in mind that nothing in your account will disappear. When you have access to Visual Automation, all the rules of your Form Connections, Sequences and Automation will work exactly as they do now. You only have a new way of connecting things.
This means that you do not need to migrate what you have configured to a new funnel now! If you are not sure, create a new funnel with Visual Automation to explore what you can do with the new Visual Automation generator.
Then, when you are ready to migrate, start with one of your simpler automation and then continue with more complex ones once you are familiar with the new system.


Key connections

Sequences

When designing your new automation, it is better to look at your sequences first. They tend to be central to any automation you have configured. When selecting your sequence, you must select a sequence with a clear objective or a sequence that connects to a sequence with a clear objective.
I will start by selecting my sequence of "Marketing":

Shapes

See all your forms that are connected to the sequence. You can see it on the Forms page on each Form card.
Observe how the "Marketing" sequence is selected.
There are a form and a landing page for this free guide. Both will be points of entry into my automation. I can combine that in a Visual Automation that looks like this:

Now that Automation is connected, I can disconnect the old Form Sequence connection on the Form Configuration page.
This works fine and you could leave it, but it is smarter in the new system to add an Event that causes the Subscriber to advance to that point when they get the "Buy: Authority" tag.

So now, if someone buys in the email 1 of the "Passage of Authority" Sequence, he will be removed to the Event and will not receive any more emails in that Sequence. But if they do not buy for a while, they will receive all the emails in the sequence until they buy.
Frequently asked questions
What happens to subscribers in old automation?

Subscribers that are currently in a sequence through the old automation will continue with that even after using that sequence within an automation. Only new Subscribers will enter the new Automation.
Do I still use the automation rules?
Yes, the Automation Rules will remain valid (available in a tab below Automation). You will still use them for some links of automation, purchases and RSS feeds.

Can trigger an automation of a purchase of Gumroad, Sam cart, etc.?

Yes. Subscribers can enter an automation through a form or a label. So to integrate with Gumroad, you would use rules to add a label when buying a product. Then create an automation that is activated when a subscriber gets that label.

When should I use an event in front of a condition?

If you want to delete someone by a custom route or send them content based on having a certain tag, you can use an Event or a Condition.
If you have a Condition after a Sequence, the Condition will wait until the Subscriber finishes the Sequence and then verify if it has the Label.
An Event will move them forward as soon as they get the Tag, even if they have only completed part of the Sequence.
Therefore, the exact time each one is used depends on what behavior you want to occur. The main question to be asked is: "Do you want the next action to take place as soon as you receive the label?" If so, use an event. If not, use a condition.
Can I activate an automation based on a specific date? For example for a webinar that happens on the day.


Yes! For that, you would use the "date occurs" event.