Why Did This MSP Need a Custom Autotask and HubSpot Integration?
Shane introduces the episode by explaining the firm's background running a managed service provider for over 25 years. That experience is what connects Innovative Automations to other MSPs now looking for help with internal operations and client-facing automation.
Hunter explains that the client was already using both Autotask and HubSpot but found the native integration between them fell short. Autotask serves as the PSA system where clients live after signing. HubSpot handles the sales side, tracking deals and opportunities. The native connector could create new companies but could not sync records in either direction in the way the client needed.
How Was the Custom Sync Actually Built?
To bridge the gap, the team created a custom field in both platforms. That shared field becomes the anchor point the automation uses to match and sync company and contact records across the two systems, something the native integration could not do on its own.
Shane notes that this approach reflects a broader shift in how integration decisions get made. Five or six years ago, tool selection was driven largely by what connected natively. Today, if a platform has an API, a custom integration is a realistic option.
How Does Data Transformation Work Between Platforms?
Hunter explains that pulling data from one platform is only part of the work. The automation also has to reformat that data so the receiving system accepts it correctly. Logic within the workflow handles this, converting values into the right type, whether that is an integer, a string, or a formatted date, before passing them to the target platform.
Shane adds a practical example. A date stored as 12/1/2025 in one system might need to arrive as "December 1st, 2025" in another. Getting the field types and formats mapped correctly is one of the most common technical hurdles in any cross-platform sync.
Why Did the Team Switch From Bidirectional to Unidirectional Sync?
The automation started as a bidirectional sync, but the team ran into a problem. When a sales record was updated in HubSpot, that change pushed into Autotask, and because Autotask was also connected to QuickBooks, the update rippled into additional systems the client did not intend to affect.
The solution was to make Autotask the declared source of truth and switch to a unidirectional flow. Now, if a record changes in HubSpot, the automation detects it and writes the authoritative Autotask value back into HubSpot, keeping everything consistent without triggering unintended updates downstream.
Shane points out a common scenario this prevents. A salesperson working quickly might misspell a company name or change capitalization. In a bidirectional setup, that small error could overwrite the correct record in Autotask or create a duplicate that then has to be cleaned up manually.
What Additional Risks Come From Built-In Platform Automations?
Hunter raises another layer of complexity. Both HubSpot and Autotask have their own internal automation tools. HubSpot workflows can trigger when a deal moves to a certain stage, and enrichment tools can update many company records at once based on date logic. If a custom sync is not designed with those internal automations in mind, they can interfere with the expected behavior and produce results no one planned for.
How Should Teams Protect Data Before Automating a Sync?
Hunter walks through the team's standard approach to data safety. The first choice is always to test inside a sandbox or demo environment in both platforms, so production data is never touched during development. When a sandbox is not available, a scoped custom field can be used to restrict the automation to a controlled subset of records only.
Beyond testing, the team requires that the client have a backup in place before any automation goes live. That can be an on-premise backup the client manages or, ideally, a backup arrangement directly with the software vendor covering daily or monthly snapshots, depending on what the business needs.
What Can This Client Add Once the Foundation Is in Place?
The current automation handles creating and syncing companies and contacts. Because the API connections and subworkflows are already built, the client can extend the automation by adding new steps to the same workflow. Planned additions include syncing tickets, creating to-do items, and pushing opportunities across both platforms.
Shane frames this as the typical growth pattern. Organizations start with one focused use case, confirm it works, then ask how to expand it. Once the two systems are speaking the same language, extending the automation becomes much more straightforward.
Could This Pattern Extend Beyond Autotask and HubSpot?
Shane confirms that the same approach could grow to include QuickBooks or any other system the client uses. The architecture is not limited to two platforms.
What Should You Do Before Bringing in an Automation Partner?
Hunter closes with a recommendation. Before or as soon as possible after engaging a partner, review the tools already in use, confirm licensing is correct, document the fields involved, and be clear about the end goal. Bringing in outside help early in the process makes it far easier to get a real return on investment rather than having to reverse-engineer decisions made before the scope was fully defined.