Preview feature
This feature is currently in preview and not yet accessible to all Tackle customers. For more information, contact [email protected].
This is the fourth article in a series guiding you through everything you need to know to set up, support, and succeed with the Tackle for Salesforce integration.
Upgrading from a previous version (You are here)
If you’ve previously used the legacy version of the Tackle - Salesforce app (versions 1.49 and prior), Tackle’s new Salesforce integration is a more substantial upgrade than previous releases. This new Tackle for Salesforce app is rebuilt from the ground up to deliver improved features and functionality, and requires fewer future app upgrades from your Salesforce administrator.
Many aspects of the new integration (referred to in this guide as v2) work very differently from the legacy integration (referred to in this guide as v1), using different Salesforce objects, requiring different permissions, and following different processes. To minimize the disruption to your Salesforce account, this guide will walk you through each stage of the upgrade, including:
Install a test version of your new Tackle for Salesforce app in Sandbox
Remove your legacy Tackle flows and buttons from Salesforce
Re-map your cloud marketplace fields into Salesforce
Replace your legacy Tackle reports in Salesforce using updated objects and fields
Deploy your new Tackle for Salesforce app to production
Deactivate your legacy Tackle - Salesforce app
Relink and backfill your co-sell and offer data
Go live!
If you haven’t previously used Tackle - Salesforce v1 and want to install a new Salesforce integration from scratch, see our article Tackle for Salesforce — Preparing to install instead.
You must be a Salesforce administrator to complete this guide
This article requires Administrator privileges in your Salesforce account to complete. If you don’t have these permissions, contact your Salesforce Administrator.
Phase 0: Prepare your Salesforce account
First, you’ll follow a few preparation steps, including setting up a Salesforce Sandbox where you’ll install the Tackle for Salesforce v2 app. Each step of this phase is explained in more detail in our guide Tackle for Salesforce — Preparing to install.
If your Salesforce Administrator doesn’t already have a Tackle login, follow step 1 of our Preparing to install guide to create a new user for your Salesforce Administrator.
Follow part 2 of our Preparing to install guide to create a new Salesforce Sandbox. Salesforce Sandboxes allow you to test changes before moving them to production. For additional help, see this guide from Salesforce: Create a Salesforce Sandbox🔗.
We recommend the following for your Sandbox type.
Partial or Full Copy Sandbox: Provides a more accurate representation of your production environment, including metadata, configuration, and sample data. Recommended for best results.
Developer Copy Sandbox: Lacks real-world data for testing. Use this if your organization has strict change control processes.
If you plan to use Salesforce to co-sell with AWS through the Amazon Partner Network Customer Engagements Program (ACE), you must follow all 8 steps of our guide Connect to AWS Partner Central to connect your Tackle account to the ACE API.
Important: If you’ve previously connected your Tackle account to the ACE API, we’ve added an additional step, titled Enable Role permissions, with an additional CloudFormation Template (CFT) that you must install for this integration. If you aren’t sure whether you’ve completed this step, open Connect to AWS Partner Central and complete Step 8: Enable Role permissions.
Phase 1: Install Tackle for Salesforce v2 in Sandbox
First you’ll install the Tackle for Salesforce v2 app, and set up permissions for your integration user, as well as each user you want to be able to use Tackle features in Salesforce.
To complete this phase, follow our guide Tackle for Salesforce — Installation guide, which explains each step in detail. A summary of that guide is included below for your reference:
Install the Tackle package in Salesforce in your new Sandbox environment. For additional help, see this guide from Salesforce: Install a managed package🔗.
If you don’t already have a separate integration user dedicated to your Tackle for Salesforce integration, you must create an integration user. For additional help, see this guide from Salesforce: Best practices for configuring your integration user🔗.
Set up permissions for your Tackle integration and users. You’ll end up making the following changes:
Create a new permission set named “Tackle - All users”
Assign the “Tackle - All users” permission set to two Permission Set Groups: “Tackle_Full_Access” and “Tackle_Integration_User”.
Assign the “Tackle_Integration_User” Permission Set Group to your Tackle integration user.
For more information about the permissions the Tackle for Salesforce app uses, see our System permissions reference guide.
Pre-authorize your Salesforce Administrators for access to your Tackle app by updating your OAuth policies. For additional help, see this guide from Salesforce: Manage OAuth Access Policies for a Connected App🔗.
Connect your Tackle and Salesforce accounts by logging in to Salesforce as your integration user.
Add the Tackle widget to your Opportunity Lightning Record page. We recommend dragging and dropping the Tackle widget to the right-hand sidebar.
Phase 2: Deactivate your Tackle v1 flows, buttons, and custom automation
The Tackle - Salesforce v1 app added several additional packaged flows and custom buttons to Salesforce as part of the installation and setup process. In order to prevent conflicts or automation errors, you’ll need to manually disable each of these.
Additionally, if your organization built any custom automation in Salesforce utilizing these flows or other data or objects from the Tackle - Salesforce v1 app, you will need to review these and adjust or remove as needed.
Deactivate Tackle flows in your Salesforce account
In this step, you’ll search your Salesforce account for any flows created by the Tackle v1 package and deactivate all of them. For additional help, see this guide from Salesforce: Deactivating Flows🔗.
In Salesforce, click the gear icon in the top-right corner of the page to access Setup. Use the quick find box🔗 to search for “Flows”. Select Flows from the search results.
Filter by Namespace: Create a List View filtering on
Flow Namespace= Tackle.For each flow with the Tackle package name, uncheck the checkbox in the Active column to deactivate them.
Click the Gear Icon in the Flows tab, then click New List View.
Enter a List View Name (e.g., "Tackle Flows"), then click Save.
Click the Filter Icon and set the following filters:
Filter by Owner: All flow definitions
Package Name: Tackle
When you’re finished, click Save.
Select each flow in this list with the Tackle package name and uncheck the checkbox in the Active column to deactivate them.
Remove screen flow from your Opportunity page
The Tackle v1 package also placed a flow on your Opportunity page, which we’ll remove next. For additional help, see this guide from Salesforce: Manage Lightning Record Pages🔗.
Navigate to an Opportunity Record.
Click the Setup Gear Icon, then click Edit Page.
Locate Flow Component: Close Co-Sell when Opportunity is Closed and click the trash icon.
When you’re finished, click Save.
Remove Buttons from the Opportunity Lightning Record Page
Navigate to an Opportunity Record.
Click the Setup Gear Icon, then click Edit Page.
Select the Highlight Panel component.
In the Actions section, find the following buttons, then click the gray x to remove them from your Opportunity Record:
Create Tackle Offer
Create Co-Sell Opportunity
Expand the following Dynamic Related Lists on your Opportunity Record, then click the trash icon to remove them:
Tackle Co-Sells
Tackle Offers
When you’re finished, click Save.
Remove the List View Button
Modify the Opportunity List View Button Layout to remove the ‘Co-Sell: Bulk Submit to the Clouds’ button.
Navigate to Setup. Search for and select “Object Manager”, then click Opportunity.
In the left menu select List View Button Layout, then click Edit.
In the Custom Buttons section, click Co-Sell: Bulk Submit to the Clouds in the Selected Buttons menu. Then, click ◀ Remove.
Click Save.
Congratulations — you’ve removed your Tackle v1 flows and buttons from Salesforce. If you have any further custom automations, take some time to test their functionality with the new integration installed, and edit or remove them as necessary.
Phase 3 - Data setup and testing
The next step is to set up the data you’ll need for your integration, including mapping fields from AWS to Salesforce. You’ll also recreate any Salesforce reports in the new app you used with the Tackle - Salesforce v1 integration, using the new fields and objects from v2. Finally, you’ll test the functionality of the new Tackle for Salesforce app, ensuring that all processes work as expected before deploying to production.
Map AWS data to your Salesforce fields
Follow our guide Map your Salesforce fields to map your fields in Salesforce to its matching data from your cloud marketplace.
Once completed, this data helps pre-fill forms to automate creating Offers and co-sells, and managing your co-sell auto-close workflow.
Create Reports & List Views
Tackle provides Report Types and default List Views in the AppExchange package. We recommend using Tackle data to clone and customize List Views, and use packaged Report Types to generate reports.
For additional help, see these guides from Salesforce:
Test Everything!
Before you deploy to production, take one last opportunity to make sure every piece of your integration works as intended. Here are a few recommended testing steps:
Verify User Permissions
Confirm assigned Permission Set Groups function as expected. For more details, see our Systems permissions reference guide.
Validate Data Mapper Setup
Ensure Offers and Co-Sells prefill correctly.
Run End-to-End Workflow Tests
Create an Opportunity → Submit Co-Sell → Verify Data Sync.
Create an Opportunity → Submit Offer
Create an Opportunity → Request a Prospect Score
Test Reports & List Views
Ensure your re-created reports and list views display expected data.
Phase 4 - Deploy your new integration into Production
Now that everything looks good in your Sandbox environment, it’s time to install the app into production. You’ve already completed each of these steps in your Sandbox environment, so this section should be pretty familiar as you push the changes you’ve already made.
Install the Tackle for Salesforce v2 App in Production
For additional help, see this guide from Salesforce: Install a managed package🔗.
Log in to your Tackle account. In the left menu, click Integrations, then click Salesforce.
Click Download from AppExchange.
Note: If you don’t see this link, you might not have access to the Tackle for Salesforce controlled availability release. Please contact [email protected] if you have been chosen for this release but don’t have access.
When you’re prompted to choose an installation environment, select your Production account.
Next, you’ll need to select which user type can access the package. Choose Install for Admins Only. You’ll set up more access and permissions after the package is installed.
When you’re finished, click Install.
Your Tackle package will now begin to install into your Salesforce sandbox environment. You can expect this step to take 15-30 minutes.
Re-create your integration user in Production and re-assign Permission Set Groups to your users
Return to our Tackle for Salesforce — Installation guide and repeat steps 3-5 to recreate your integration user and manage permissions for your integration and users in Production instead of in Sandbox. You’ll make the following changes:
Create a new permission set named “Tackle - All users”
Assign the “Tackle - All users” permission set to two Permission Set Groups: “Tackle_Full_Access” and “Tackle_Integration_User”.
Assign the “Tackle_Integration_User” Permission Set Group to your Tackle integration user.
For additional help, see our System permissions reference guide, as well as these guides from Salesforce:
Connect Salesforce to Tackle Production
Return to our Tackle for Salesforce — Installation guide and repeat steps 6 and 7 to reconnect your Salesforce account to Tackle in production and add the Tackle widget to your Lightning Opportunity Record.
As the Integration User, sign in to Salesforce and complete the connection step outlined in the Tackle for Salesforce Setup Guide. This step ensures authentication and access permissions are correctly configured. Select your Production Tackle Vendor when connecting your Salesforce Org.
Complete the Production Vendor Data Mapper
Return to our guide Map your Salesforce fields and repeat the data mapping you completed in Sandbox, but map your fields in your Production environment instead.
Relink and backfill co-sell & offer data
If you used the v1 app for Co-sell or Offers, you need to move your data to the new app before severing the v1 connection. Offers data will populate in the new app automatically, and you’ll need to follow the steps below for Co-sell:
Follow our guide Link and relink AWS co-sells to Salesforce opportunities to enable automation for your co-sells and offers in Salesforce.
Follow this guide from Salesforce to Build a report🔗. For your reporting data, select the Tackle co-sell object.
Export your report🔗 as a .csv or Excel spreadsheet file.
Deploy a Change Set from Sandbox to Production
In this step, you’ll package all the changes you made so far in your Sandbox into a Change Set, then deploy that change set in Production. For more help, see this guide from Salesforce: Change Sets🔗.
In Salesforce, return to your Sandbox.
Navigate to Setup. Search for and select “Outbound Change Sets”, then click Outbound Change Sets🔗.
Create a new outbound Change Set and click Add components, then add all of the changes you made in Phases 1-3 of this guide, including:
List Views
Reports
Lightning Record Pages
Custom Flows
Apex Classes and Triggers
Custom Permission Sets
For more help, see this guide from Salesforce: Select Components for an Outbound Change Set🔗. When you’re finished, click Save.
Return to your Production account and navigate to Setup. Search for and select “Inbound Change Sets”, then click Inbound Change Sets.
Find the change set you made from your Sandbox and click Deploy. For more help, see this guide from Salesforce: Deploy a Change Set🔗.
Profiles and Permission Sets do not deploy with Change Sets and need to be manually assigned. You’ll recreate those slightly later in this guide.
Deactivate the Connection from Salesforce to Tackle
In Salesforce, navigate to the App Launcher, then search for and select “Tackle Setup Assistant”. This is the setup assistant for the v1 app.
Next to System Connections, click “Edit” or “Continue”.
On the Connect to Tackle system connection, click “Disconnect”
Navigate to Setup, then search for and select “Connected Apps OAuth Usage”.
Next to ‘TackleRefreshToken’, select Uninstall.
Deactivate Legacy Tackle Flows
Repeat Phase 3 of this guide for your Production account instead of sandbox to deactivate Tackle legacy flows in production, as well as all custom Tackle buttons and any other custom automation you may have enabled. Non-packaged Tackle flows and Apex classes may be disabled via a deployment with Change Sets.
For additional help, see this guide from Salesforce: Deactivating Flows🔗.
Go-Live!
You’re now ready to use the Tackle for Salesforce app in production! To ensure a smooth transition:
Monitor reports and list views to verify data accuracy and ensure users can access necessary records.
Work with users to confirm they have the correct permissions and can perform their tasks without restrictions.
Ensure active Co-Sells and Offers have been migrated properly and are functional.
Validate that updates to Co-Sells and Offers are being processed correctly and that users have access to all relevant data.
Final Step: Uninstall the Legacy App
Once the legacy package is fully disconnected, Tackle recommends uninstalling it to:
Free up Salesforce org limits, including data storage and custom object quotas.
Prevent conflicts with the new Tackle for Salesforce app, ensuring a cleaner system.
Reduce confusion for users by removing outdated components from page layouts and automation workflows.
For more help, see this guide from Salesforce: Uninstall a Managed Package🔗.
Check for Dependencies:
Identify reports, list views, flows, automation, and Lightning Record Pages that reference legacy fields, objects, or actions.
Ensure all references are removed before attempting to uninstall.
Backup Data:
Export any historical data from the legacy package if needed for reference.
Remove Dependencies:
Delete any flows, validation rules, or automation tied to legacy objects.
Update Lightning Record Pages to remove references to Tackle v1 components.
Uninstall the Managed Package:
Navigate to Setup → Installed Packages.
Find the Find the Tackle package (namespace: tackle).
Click Uninstall, select Backup Data Option, and confirm the uninstallation.
Verify Uninstallation:
Ensure that all legacy fields, objects, and automations have been removed.
Confirm that no remaining dependencies exist in reports, list views, or workflows.