1. Documentation /
  2. How to migrate from Follow-Up Emails

How to migrate from Follow-Up Emails

Overview

↑ Back to top

This document describes how to migrate from the Follow-Up Emails extension to the AutomateWoo extension.


Please see Follow-Up Emails vs AutomateWoo for a comparison between these two extensions.

Migration

↑ Back to top

The migration from Follow-Up Emails to AutomateWoo is a manual process and all existing workflows will need to be created manually by setting up similar options in AutomateWoo. Refer to the generic steps below for help in the migration process:

  1. Install, activate, and set up the AutomateWoo extension.
  2. Go to Follow-Up > Emails and open a “Follow-Up Email” workflow that you want to migrate.
  3. Go to AutomateWoo > Workflows, click “Add Workflow” and add a title.
  4. Make note of the selected trigger from the “Follow-up Details” meta box and find an equivalent AutomateWoo trigger for it from the mappings here.
  1.  Select the equivalent AutomateWoo Trigger in the workflow trigger dropdown.

    Note: Some triggers have options to run only for specific scenarios. For example, “After File Downloaded” trigger enables the “Downloadable Files” option, allowing you to select the specific file you want to run the trigger on.
  2. Follow-Up Emails provides options to select a “Product” and/or “Category” and will only run triggers for those specific matches. AutomateWoo provides similar triggers, so be sure to check if a product or category is selected in the Follow-Up Emails workflow and add similar rules to the AutomateWoo workflow.
  3. Match any additional Rules set in the Follow-up Emails workflow and add similar Rules to the AutomateWoo workflow.
  1. Set workflow timing similar to Follow-Up Emails (Sending Delay) in the “Timing” meta box by selecting the “Delayed” option.

  2. Open the “Settings” tab and add equivalent rules to AutomateWoo. More detailed information on each setting is provided here.
    Follow-Up Emails:


    AutomateWoo:


AutomateWoo provides the “Workflow – Run Count for Customer” rule to limit the number of workflow runs for each customer. To migrate the Follow-Up Emails’ “Send once per customer” setting to AutomateWoo, we can add the rule Workflow – Run Count for Customer – “is” – 0 to make it run only once per customer. Once the workflow’s run count has reached 1, this rule will prevent it from running a second time for the specific customer.

  1. Open the “Coupons” tab and check if “Generate a Coupon Code” is checked. Create a template coupon by following the guide here.
  2. Open the “Exclusions” tab and add equivalent rules to AutomateWoo.
    Follow-Up Emails:

AutomateWoo:

  1. Click “Add Action” in the actions section and Select “Send Email” action.
    Note: AutomateWoo has multiple actions to choose from (Send Email, Updating Order, Customer Data, etc.).
  2. Add the value {{customer.email}} to the “To:” field. Follow-Up Emails doesn’t have a To field value as it always sends emails to the customer, while AutomateWoo provides a To field which supports variables and multiple emails.
  3. Open the “From” tab and fill in the “Reply to” fields.
    Follow-Up Emails:


    AutomateWoo:

  4. Add an “Email subject”, “Email heading”, and “Email preheader” accordingly.
  5. Copy email content from Follow-Up Emails to the new workflow. Replace Follow-Up Emails variables with AutomateWoo variables. Equivalent AutomateWoo variables can be found here.
    Follow-Up Emails:

AutomateWoo:

  1. Open the “Google Analytics” tab and enable tracking if needed. Also, add your “Link Tracking” information if used. Check the checkbox for “Enable Conversion Tracking”, conversion tracking is always enabled in Follow-Up Emails, but in AutomateWoo it needs to be enabled separately for each workflow.
    Follow-Up Emails:


    AutomateWoo:

  2. Follow-Up Emails has custom email templates, which can be added and edited from the WordPress Admin and then used dynamically to add information anywhere in a template using {section:*}…{/section:*}. To use the same template in an AutomateWoo workflow, you can add the “Send Email – Raw HTML” action and migrate all the template HTML to it. Equivalent variables will need to be replaced. AutomateWoo also offers support for custom email templates and design customization. For more information, please visit AutomateWoo’s documentation page on the topic.
  3. Click the Preview link to preview your email and ensure it appears as expected.
  4. Save Workflow… Done!


Notes

  • AutomateWoo comes with pre-configured workflows (Presets) that you can choose from to quickly and easily create your own workflows. You can check if any of the presets match your Follow-Up Emails and you can directly create a workflow with a single click. They include example content that you can build upon and modify to meet your store’s unique needs (see more information here).
  • Some Follow-Up Emails features are missing in AutomateWoo. You can learn more about that here.

Examples

↑ Back to top

Some migration examples are given below to provide more details on the process.

1. A welcome email for new customers with coupon

Follow-Up Emails:
This workflow sends a welcome email with a 10% off coupon code when someone makes their first purchase. 

Follow the steps below to migrate this workflow to AutomateWoo:

  1. Create a new workflow.
  2. Select the Order Completed trigger.
  3. Select the Order Is Customers First = Yes rule.
  4. Click “Add Action” and select Send Email and include the variable {{ customer.email }} as the email address.
  5. Populate the required fields.
  6. Craft the content of the email by replacing variables with equivalent AutomateWoo variables. For more information on creating personalized coupons, please refer to the documentation here
  7. Click the Preview link to preview your email to ensure it appears as expected.
  8. Save Workflow… Done!


Migrated workflow should look like this.

2. Reward repeat customers with a coupon

Follow-Up Emails:
This workflow sends an email with a coupon code to reward customers who spent over $100 and have ordered at least 3 times.

Follow below steps to migrate this workflow to AutomateWoo:

  1. Create a new workflow.
  2. Select the Order Completed trigger.
  3. Select the Customer – Order Total “is greater than” 3 rule.
  4. Select the Customer – Total spent “is greater than” 100 rule.
  5. Select the Workflow – Run Count For Customer “is” 0 rule to send an email to customer only once. As we are using the Customer – Total Spent rule, once the threshold is reached the workflow will run every time the customer places an order.
  6. Click Add Action and select Send Email and include the variable {{ customer.email }} as the email address.
  7. Populate the required fields.
  8. Craft the content of the email, including the personalized coupon variable. For more information on creating personalized coupons, please refer to the documentation here
  9. Click the Preview link to preview your email to ensure it appears as expected.
  10. Save Workflow… Done!

Migrated workflow should look like this.

Equivalent Triggers

↑ Back to top

Equivalent AutomateWoo triggers as compared to Follow-up Emails triggers are listed below. More detailed information on each Follow-Up Emails trigger can be found here and each  AutomateWoo trigger here.

Some of Follow-up Emails triggers are not available in AutomateWoo in exactly the same way. So those equivalent triggers should be added with a Trigger + Rule combination.

Purchase Email Triggers

↑ Back to top
Follow-Up EmailsAutomateWoo
after first purchaseTrigger: Order Processing/Order Completed+Rule: Order – Is Customer’s First = Yes
after added to cartCart Abandoned triggers
after customer purchased more than one timeTrigger: Order Processing/Order Completed+Rule: Customer – Order Count “is greater than” 1
after downloadable file addedExact same trigger is not available in AutomateWoo, similar trigger is:Downloadable Product Purchased
after file downloadedFile Downloaded
file not yet downloadedFile Not Yet Downloaded
after Coupon usedTrigger: Order created+Rule: Order – Coupons “matches any” Coupon
after Order Status: anyOrder Status Changes/Order [status]
after refunded manuallyOrder Refunded Manually
after refunded successfullyOrder Refunded

Signup Email Triggers

↑ Back to top
Follow-Up EmailsAutomateWoo
after user signs upCustomer Account Created
after user signs up to a list(Not available in AutomateWoo)

Re-Engagement Email Triggers

↑ Back to top
Follow-Up EmailsAutomateWoo
after last purchaseTrigger: Order Processing/Order Completed+Rule: Customer – Last Paid Order Date “is not in the last” – X – Days/Hours
after order total is aboveTrigger: Order Processing/Order Completed+Rule: Order – Total “is greater than” – X
after order total is belowTrigger: Order Processing/Order Completed+Rule: Order – Total “is less than” – X
after customer purchased more than one timeTrigger: Order Processing/Order Completed+Rule: Customer – Order Count “is greater than” 1
after total orders by customer is equal toTrigger: Order Processing/Order Completed+Rule: Customer – Order Count “is” X
after total orders by customer is greater thanTrigger: Order Processing/Order Completed+Rule: Customer – Order Count “is greater than” X
after total purchase amount by customer is equal toTrigger: Order Processing/Order Completed+Rule: Customer – Total Spent “is” X
after total purchase amount by customer is greater thanTrigger: Order Processing/Order Completed+Rule: Customer – Total Spent “is greater than” X

Subscription Email Triggers

↑ Back to top
Follow-Up EmailsAutomateWoo
after subscription activatedTrigger: Subscription Status Changed
Status changes from: [Any]
Status changes to: Active
after subscription renewedSubscription Renewal Payment Complete
after subscription cancelledTrigger: Subscription Status Changed
Status changes from: [Any]
Status changes to: Cancelled
after subscription pending cancellationTrigger: Subscription Status Changed
Status changes from: [Any]
Status changes to: Pending Cancellation
after subscription expiredTrigger: Subscription Status Changed
Status changes from: [Any]
Status changes to: Expired
after subscription suspendedTrigger: Subscription Status Changed
Status changes from: Active
Status changes to: On Hold
after subscription reactivatedTrigger: Subscription Status Changed
Status changes from: On Hold
Status changes to: Active
after subscription renewal payment failedSubscription Renewal Payment Failed
after a renewal order has been createdTrigger: Subscription Order Created
Subscription order types: Renewal
before next subscription paymentSubscription Before Renewal
before active subscription expiresSubscription Before End

WooCommerce Booking Triggers

↑ Back to top
Follow-Up EmailsAutomateWoo
Before Booked Date(Not available in AutomateWoo)
After Booked Date(Not available in AutomateWoo)
After Booking is CreatedBooking Created
After Booking Status: [Status]Trigger: Booking Status Changed
Status changes from: [Any]
Status changes to: [Status]

WooCommerce Memberships Triggers

↑ Back to top
Follow-Up EmailsAutomateWoo
before membership expires(Not available in AutomateWoo)
after membership status: [Status]Trigger: Membership Status Changed
Status changes from: [Any]
Status changes to: [Status]

Sensei LMS Triggers

↑ Back to top
Follow-Up EmailsAutomateWoo
after selecting a specific answerSpecific Answer Selected
after signed up to a courseSigned Up To a Course
after course is completedCourse Completed
after lesson is startedLesson Started
after lesson is completedLesson Completed
after completing a quizQuiz Completed
after passing a quizQuiz Passed
after failing a quizQuiz Failed
after lesson added(Not available in AutomateWoo)

WooCommerce Points and Rewards Triggers

↑ Back to top
Follow-Up EmailsAutomateWoo
After: Points Earned(Not available in AutomateWoo)
Earned Points per order is greater than(Not available in AutomateWoo)
Total earned points is greater than(Not available in AutomateWoo)


Note: AutomateWoo does not support Twitter, The Events Calendar, or WooTickets.

Equivalent Variables

↑ Back to top

Equivalent AutomateWoo variables as compared to Follow-up Emails variables are listed below. More detailed information on each Follow-Up Emails variable can be found here.

All generic variables

↑ Back to top
Follow-Up EmailsAutomateWoo
{item_names}{{ order.items | template: ‘list-comma-separated’ }}
{item_names_list}{{ order.items | template: ‘list-comma-separated’ }}
{item_prices}Use {{ order.items }} with available template options.
{item_prices_image}
{item_codes_prices}
{item_prices_categories}
{item_categories}
{dollars_spent_order}{{ order.total }}
{customer_username}{{ customer.username }}
{customer_first_name}{{ customer.first_name }}
{customer_last_name}{{ customer.last_name }}
{customer_name}{{ customer.full_name }}
{customer_email}{{ customer.email }}
{order_number}{{ order.number }}
{order_date}{{ order.date | format: ‘site’ }}
{order_datetime}{{ order.date | format: ‘mysql’ }}
{order_subtotal}{{ order.subtotal }}
{order_tax}{{ order.meta | key: ‘_order_tax’ }}
{order_pay_method}{{ order.payment_method }}
{order_pay_url}{{ order.payment_url }}
{order_billing_address}{{ order.billing_address }}
{order_billing_phone}{{ order.billing_phone }}
{order_shipping_phone}(Not available in AutomateWoo)
{order_shipping_address}{{ order.shipping_address }}
{coupon_code}{{ customer.generate_coupon }}
{coupon_code_used}(Not available in AutomateWoo)
{coupon_amount}(Not available in AutomateWoo)
{store_url}{{ shop.url }}
{store_url_secure}{{ shop.url }}
{store_url=path}{{ shop.url }}
{store_name}{{ shop.title }}
{unsubscribe_url}{{ customer.unsubscribe_url }}
{post_id=xx}(Not available in AutomateWoo)
{download_url}{{ download.url }}
{download_filename}{{ download.file_name }}
{webversion_url}(Not available in AutomateWoo)
{webversion_link}(Not available in AutomateWoo)
{amount_spent_order}{{ order.total }}
{amount_spent_total}{{ customer.total_spent }}
{number_orders}{{ customer.order_count }}
{last_purchase_date}(Not available in AutomateWoo)
{cart_contents}{{ cart.items }}
{cart_total}{{ cart.total }}
{cart_url}{{ cart.link }}
{refund_amount}{{ refund.amount }}
{refund_reason}{{ refund.reason }}
{cf ID field_name}(Not available in AutomateWoo)

Product variables

↑ Back to top

AutomateWoo’s product variables are not always available. They will only be available when the trigger is related to a specific product, such as a booking or review which is linked to a specific product.

Follow-Up EmailsAutomateWoo
{item_name}{{ product.title }}
{item_code}{{ product.sku }}
{item_url}{{ product.permalink }}
{item_category}(Not available in AutomateWoo)
{item_price}{{ product.current_price }}
{item_quantity}(Not available in AutomateWoo)

WooCommerce Booking variables

↑ Back to top
Follow-Up EmailsAutomateWoo
{item_name}{{ product.title }}
{item_category}(Not available in AutomateWoo)
{item_quantity}(Not available in AutomateWoo)
{booking_start}{{ booking.start_date | format: ‘mysql’ }}
{booking_end}{{ booking.end_date | format: ‘mysql’ }}
{booking_duration}(Not available in AutomateWoo)
{booking_date}{{ booking.start_date | format: ‘site’ }}
{booking_time}{{ booking.start_time }}
{booking_amount}{{ booking.cost }}
{booking_resource}{{ booking.resource }}
{booking_persons}{{ booking.persons }}

Sensei LMS variables

↑ Back to top
Follow-Up EmailsAutomateWoo
{course_name}{{ course.title }}
{course_url}{{ course.url }}
{course_link}{{ course.url }}
{course_results_url}{{ course.results_url }}
{certificate_url}{{ course.certificate_url }}
{certificate_link}{{ course.certificate_url }}
{lesson_name}{{ lesson.title }}
{lesson_url}{{ lesson.url }}
{lesson_link}{{ lesson.url }}
{quiz_url}{{ quiz.url }}
{quiz_link}{{ quiz.url }}
{quiz_grade}{{ quiz.grade }}
{quiz_passmark}{{ quiz.passmark }}
{teacher_first_name}{{ teacher.first_name }}
{teacher_last_name}{{ teacher.last_name }}
{teacher_name}{{ teacher.full_name }}

Subscription variables

↑ Back to top
Follow-Up EmailsAutomateWoo
{subs_start_date}{{ subscription.start_date | format: ‘mysql’ }}
{subs_end_date}{{ subscription.end_date | format: ‘mysql’ }}
{subs_renew_date}{{ subscription.next_payment_date | format: ‘mysql’ }}
{days_to_renew}(Not available in AutomateWoo)
{subs_trial_length}(Not available in AutomateWoo)
{subs_first_payment}(Not available in AutomateWoo)
{subs_cost_term}(Not available in AutomateWoo)
{subs_cost}{{ subscription.total }}
{subs_id}{{ subscription.id }}

WooCommerce Membership variables

↑ Back to top
Follow-Up EmailsAutomateWoo
{membership_plan}{{ membership.plan_name }}
{membership_plan_discounts}(Not available in AutomateWoo)
{membership_renew_url}{{ membership.renewal_url }}
{membership_end_date}{{ membership.date_expires | format: ‘mysql’ }}
{membership_start_date}{{ membership.date_started | format: ‘mysql’ }}

Points and Rewards variables

↑ Back to top
Follow-Up EmailsAutomateWoo
{current_points}{{ customer.points }}
{points_earned}(Not available in AutomateWoo)
{reward_event_description}(Not available in AutomateWoo)

Note: AutomateWoo does not support Twitter, The Events Calendar, or WooTickets.