Before you build a bundle in Solution Launchpad, know what will actually install. Not every asset is compatible with every edition of Keap — some features install but require additional setup, some install silently and cannot be used, and some will cause the installation to fail entirely. This reference covers edition compatibility for every asset type available in Solution Launchpad so you can build bundles that work correctly for your clients.
Solution Launchpad is available through the Keap certified partner program. To become a certified partner, visit the Keap Certified Partner page.
This article covers edition compatibility for standalone assets, Advanced Automation triggers, and Advanced Automation actions. Use the tables below before distributing a bundle to confirm that every asset in the bundle is compatible with your client's edition.
How to Read the Compatibility Tables
Each table shows compatibility for Pro, Max, Ultimate, and Classic editions at the time of install. The Exceptions / Notes column provides additional context for assets that have conditions, limitations, or known issues. The symbols used in the tables mean the following:
- ✓ — this asset is fully compatible with this edition and will install without issues
- ⚠ — this asset is compatible with this edition but may require additional setup after install, or may produce errors if certain conditions are not met
- X — this asset is not compatible with this edition
Standalone Asset Compatibility
The following table shows edition compatibility for standalone assets — individual items that can be exported and installed independently of an automation.
| Feature | Pro | Max | Ultimate | Classic | Exceptions / Notes |
|---|---|---|---|---|---|
| Tags | ✓ | ✓ | ✓ | ✓ | |
| Custom Roles and Permissions | ✓ | ✓ | ✓ | ✓ | |
| Email Broadcasts (new builder) | ✓ | ✓ | ✓ | ✓ | |
| Custom Fields | ✓ | ✓ | ✓ | ✓ | If a custom field with the same name but a different field type already exists in the destination app, the install will fail with an error describing the conflict. If the installing user has reached the custom field limit for their edition, the install will also fail with an error describing the limit. |
| New Landing Page | ⚠ | ✓ | ✓ | ✓ | Pro users will receive a validation message if the landing page bundle contains more than 2 pages. |
| Convrrt Landing Page | ✓ | ✓ | ✓ | ✓ | The paid Convrrt add-on is required for full functionality. Installation will fail if the receiving user's account does not have the Convrrt add-on active. |
| New Email Builder Saved Templates ("My Templates" in the email builder) | ✓ | ✓ | ✓ | ✓ | Only the email body content is shared. The subject line and pre-header text are not part of the saved template — those are set at the automation or broadcast level where the template is used. |
| New Internal Form | ✓ | ✓ | ✓ | X | Install is technically allowed on Classic, but the form cannot be used or located unless the user switches to Ultimate view. |
| New Public Form | ✓ | ✓ | ✓ | X | Install is technically allowed on Classic, but the form cannot be used or located unless the user switches to Ultimate view. |
| New Appointments | ✓ | ✓ | ✓ | X | Install is technically allowed on Classic, but appointments cannot be used or located unless the user switches to Ultimate view. |
| Landing Page Popups | ✓ | ✓ | ✓ | X | Install is technically allowed on Classic, but popups cannot be used or located unless the user switches to Ultimate view. |
| Visual Pipelines | ✓ | ✓ | ✓ | X | Install is technically allowed on Classic, but pipelines cannot be used or located unless the user switches to Ultimate view. |
| Coaching Portal Plays | ✓ | ✓ | ✓ | X | Install is technically allowed on Classic, but plays cannot be used or located unless the user switches to Ultimate view. Internal link options for plays differ between Pro, Max, and Ultimate — test all links in the intended edition before distributing to clients. |
| Easy Automations | ✓ | ✓ | ⚠ | X | Install is technically allowed on Classic, but Easy Automations cannot be used or located unless the user switches to Ultimate view. Easy Automations installed in Ultimate will run but may produce unexpected results and cannot be visually edited in Ultimate. |
| Checkout Forms | ⚠ | ✓ | X | X | Checkout forms that include a promo code field cannot be installed to Pro accounts. |
| Text Templates | X | X | X | X | Text templates are not currently enabled for any edition. Do not include text templates in bundles intended for distribution. |
| Saved Searches | ⚠ | X | ⚠ | X | Currently in alpha with a limited number of partners. Extreme caution required — search criteria must be verified to work correctly in the destination app's edition before distributing. |
Advanced Automation Compatibility
Advanced Automations have a large number of components with edition-specific compatibility rules. The compatibility tables below are divided into two sections — triggers (the "When" conditions that start an automation) and actions (the "Then" steps the automation performs). Review both sections when building any Advanced Automation bundle intended for distribution across editions.
Automation Triggers (When's)
| Trigger | Pro | Max | Ultimate | Classic | Exceptions / Notes |
|---|---|---|---|---|---|
| Tag is applied | ✓ | ✓ | ✓ | ✓ | |
| Email link is clicked | ✓ | ✓ | ✓ | ✓ | |
| API trigger | ✓ | ✓ | ✓ | ✓ | |
| Quote status changes | ✓ | ✓ | ✓ | ✓ | |
| Landing page (new builder) | ✓ | ✓ | ✓ | ✓ | |
| WordPress opt-in | ✓ | ✓ | ✓ | ✓ | |
| Legacy web form is submitted | ✓ | ✓ | ✓ | ✓ | |
| Product is purchased | ✓ | ✓ | ✓ | ✓ | Product category is shared but the specific product name is not copied over. |
| Failed purchases | ✓ | ✓ | ✓ | ✓ | Specific products referenced in this trigger are not supported and will be removed from the solution during cloning. |
| Pipeline stage is moved | ✓ | ✓ | ✓ | X | Install is technically allowed on Classic, but the trigger cannot be used or located unless the user switches to Ultimate view. |
| Lead score is achieved | X | ✓ | ✓ | ✓ | Pro users will see a missing features error referencing lead score and the install will fail. Do not include this trigger in bundles intended for Pro accounts. |
| Notes on Automation Canvas | ✓ | ✓ | ✓ | X | Notes created in the legacy automation builder may display with broken formatting in the new automation builder, and vice versa. Classic users may need to switch to Ultimate and the new automation builder to view notes correctly. |
| Task is complete | ⚠ | ⚠ | ⚠ | ⚠ | Task outcomes are not copied. This trigger and any related Create Task actions will require re-configuration in the destination app after install. |
| Note is applied | X | X | ✓ | ✓ | This trigger is not compatible with Pro or Max editions. Bundles containing this trigger cannot be installed to Pro or Max accounts. |
| Create Appointments [legacy] | X | X | ✓ | ✓ | Pro and Max users will see a missing features error and the install will fail. |
| Internal Form is submitted [legacy] | X | X | ✓ | ✓ | Pro and Max users will see an error referencing missing Keap Ultimate Automation Builder features. The error message does not specify the legacy internal form as the cause. |
| Opportunity stage moved [legacy] | X | X | ✓ | ✓ | Pro and Max users will see a missing features error referencing legacy opportunities and the install will fail. Opportunity defaults, custom fields, and custom win/loss reasons are not copied. |
| Action sets [legacy] | X | X | X | X | Action sets are not available in Solution Launchpad and cannot be included in any bundle. |
Automation Actions (Then's)
| Action | Pro | Max | Ultimate | Classic | Exceptions / Notes |
|---|---|---|---|---|---|
| Apply or remove tag | ✓ | ✓ | ✓ | ✓ | |
| Send email (new email builder) | ✓ | ✓ | ✓ | ✓ | |
| Get email opt-in | ✓ | ✓ | ✓ | ✓ | |
| Apply a note | ✓ | ✓ | ✓ | ✓ | |
| Empty sequence | ✓ | ✓ | ✓ | ✓ | |
| Add or remove from sequence | ✓ | ✓ | ✓ | ✓ | Adding a contact to a sequence in a different campaign may produce errors or unexpected results. Verify cross-campaign sequence references before distributing. |
| Date timer | ✓ | ✓ | ✓ | ✓ | The receiving user should verify that the timer's time setting is correct for their time zone after installing. |
| Delay timer | ✓ | ✓ | ✓ | ✓ | The receiving user should verify that the timer's time setting is correct for their time zone after installing. |
| Appointment timer (new appointments) | ✓ | ✓ | ✓ | X | Install is technically allowed on Classic, but the appointment timer cannot be used or located unless the user switches to Ultimate view. |
| Create deal | ✓ | ✓ | ✓ | X | Install is technically allowed on Classic, but the Create Deal action cannot be used or located unless the user switches to Ultimate view. |
| Create an invoice | ✓ | ✓ | ⚠ | ⚠ | Pro and Max do not support auto-charge payment options — if the action is configured with auto-charge, it will appear unconfigured after install. "Create Order" in Classic and Ultimate is converted to "Create Invoice" in the new automation builder for Pro and Max. Verify that invoice functionality works as expected in the destination edition before distributing. |
| Assign an owner (Round Robin) | ⚠ | ⚠ | ✓ | ✓ | Round robin configuration is not copied. This action will require re-configuration in the destination app. When installed to Pro or Max, the action will visually appear to have a round robin configured but will not function as a round robin — this is a known display issue. |
| Set field value | ⚠ | ⚠ | ✓ | ✓ | Pro and Max do not support date/time custom fields. If the automation references a date/time custom field, the install will fail on Pro and Max with an error describing the incompatibility. |
| Field timer | ⚠ | ⚠ | ✓ | ✓ | Pro and Max do not support date/time custom fields. If the automation references a date/time custom field, the install will fail on Pro and Max with an error describing the incompatibility. |
| Create a task | ⚠ | ⚠ | ⚠ | ⚠ | Task outcomes are not copied. This action and any related Task is Complete triggers will require re-configuration in the destination app after install. |
| Send an HTTP Request | ⚠ | ⚠ | ⚠ | ⚠ | HTTP request configuration is not copied — the action installs empty and must be rebuilt in the destination app before it will function. |
| Send text message | ⚠ | ⚠ | ⚠ | ⚠ | The message content is not copied. The action will install to all editions except free trial, but the message must be written in the destination app before the action will send anything. |
| Create an Opportunity [legacy] | X | X | ⚠ | ⚠ | Opportunity defaults, custom fields, and custom win/loss reasons are not copied. Opportunities are not being actively improved — consider using the Deals object in Pro, Max, or Ultimate instead. |
| Send email (legacy BARD builder) | X | X | X | X | Currently users see a warning but can proceed with export and install. This will be disabled in a future update and export and install will fail with a clear error message. Rebuild any legacy BARD emails in the new email builder before including them in bundles. |
Comments
0 comments