Backing Up Your Troops: A Field Guide

Back up your workflows, folks. You have until Nov. 30 until Troops.ai is deprecated and its owner, Salesforce, pushes users to a totally different software, Slack Sales Elevate. 

Here’s the email:

‍

‍

‍What is Slack Sales Elevate? 

It is a new integration for rep-level productivity, not a full-throated process solution. It comes with higher costs and less flexibility on the pricing side. Ultimately, Elevate is not a Troops analog. 

Obviously, aside from the costs and hassles of trying to fit a square peg in a round hole, you can’t afford to lose this kind of vital information. Your workflows are more than just your intellectual property, they’re also your… ya know… whole business advantage. 

So, we whipped up a quick and dirty guide to backup your Troops workflows, regardless of where you go from here (though it should be us, Rattle).

Note: If you're already looking for a Troops alternative that's — ya know — an alternative, we’ve been waiting for you. Grab a few minutes with us at our Book a Demo page to to find out how we can help.

Step 1: Export your data

Here is an easy Gsheet template to help you with the initial export of your Troops data. (The orange columns will populate automatically upon export. The green columns are the important ones that you’ll need to grab and transport over).

1. In Troops, export workflows (screenshot above).
2. As we said, the export will contain the fields in orange on the template we’ve provided above. There is a field that indicates if the signal is active or not.
3. For each workflow, add the goal, conditions, recipient and opening message to the sheet. (Additionally, this is a great opportunity to evaluate if a Troops active signal should be carried forward to Rattle.)

‍

Step 2: Assess your current workflows

Now, before you can sound the retreat from Troops(AI) territory, a clear understanding of your existing terrain is crucial. 

While Troops did not have advanced analytics to show performance/reporting that would give you the individual-level, you’ll be able to collect information from your basic dash, enough to sketch your process.

Here's how to approach everything else.

• Inspect the Trenches: Examine every integration, and identify all the elements that make your current system tick. Understand the triggers, actions, and the conditions in which they operate.
• Survey the Damages: Are there any feature gaps you’ve realized are critical now that you’ve used Troops? Now’s the time to address them. Are there any delayed alerts, limited customization, or missing analytics? Document these weaknesses, as they will inform your next steps.
• Map the Landscape: Create a visual map of your current workflows. This will serve as a reference when transitioning to a new system. Include every step, from initiation to completion, along with any dependencies or contingencies.
• Gather the Forces: Consult with all stakeholders, including sales, marketing, and customer success teams. Their insights are essential for understanding what works well and what needs improvement.

(Not for not, Rattle’s huge new secret tool can help you, book a demo here)

‍

Step 3: Document everything you can

Documentation is the foundation of a successful transition to... well... most anything. 

Here's a tactical approach:

• Create a Battle Plan: With all the info in-hand, it’s time to define what needs to be documented. Include triggers, actions, dependencies, rules, and any custom configurations. You can utilize tools like process flow diagrams, spreadsheets, or specialized documentation software to capture every detail.
• Record the Intelligence: Don't just note what each workflow does; be extra sure to write down why it does what it does. This extra context will be absolutely vital in replicating or improving these processes in a new environment.
• Maintain your War Journal: Keep a running log of your entire process, private! This will be valuable not only for the current transition but for future reference or onboarding new team members.

‍

Step 4: Evaluate new solutions

Choosing a new process-enhancing platform requires careful consideration of both features and alignment with your existing workflows. It could be Rattle. It could not be.

Here's how to strategize:

• Analyse Alternatives: Obviously, there’s us. But make sure to do your research and create a shortlist of platforms that offer capabilities aligning with your current needs. Look for flexibility, compatibility with existing tools, and room for future growth.

• Run Recon: Request demos, start free trials, or engage with sales representatives of the potential platforms. Direct hands-on experience will give you insights into how they will fit within your ecosystem.

• Consult Allies: Consult with the likes of RevOps communities, RevOps Coop for example, which has a tools and software channel.

• Perform a SWOT Analysis: Assess the Strengths, Weaknesses, Opportunities, and Threats of each potential platform. This analysis will help you compare them objectively.

• Plan for Integration: Consider how the new platform will integrate with other systems, how long it will take to install, how much effort it will take to manage, and the time it will take to arrive to proficiency.

‍

Step 5: Execute Retreat

Once you've selected a new platform, it's time to make the transition.

Here are the steps:

• Develop a Migration Plan: Break down the migration into manageable tasks and phases. Outline timelines, allocate resources, and establish clear responsibilities.

• Train Your Own Troops: Conduct training sessions for all relevant team members on the new platform. Provide resources, guides, and support to ensure a smooth learning curve. (For those deciding to come to Rattle, our Enablement tool can help you do this automatically).

• Migrate with Precision: Use your detailed documentation from Step 1 to guide the migration. Test each workflow thoroughly to ensure it operates as expected.

• Monitor the Frontlines: Keep a close eye on the transition, regularly checking for issues and addressing them promptly. Open lines of communication with your team to gather feedback and make necessary adjustments.

• Celebrate Victory: Once the migration is successful, celebrate the achievement with your team. Maybe with some amazing GIFs. Reflect on the lessons learned and document the process for future reference.

• Provide Ongoing Support: Offer continuous support to ensure that everyone is comfortable with the new platform. Regular check-ins, additional training, or refining workflows as needed will help sustain success.

By rigorously evaluating and documenting your current state with Troops(AI), you'll be well-prepared to make a smooth and effective transition to a new platform. Your success in this first phase of retreat sets the stage for the subsequent recovery and reconnection, ensuring that you remain on-task, on-track, and on-target.