Our business is not so much transactional as it is focused on building industry relationships (i.e. OEM partners) first that will result in revenue generation afterward.
We’re seriously considering the ABM function as a better paradigm of operarions for our business model, but the caution about it being irreversible gives me a moment of pause. If we ‘flip the switch’, will it affect any legacy work we’ve done or limit us from directly using the automations or functions we’ve already set up?
Essentially I’m concerned about any unintended consequences or ‘collatral damage’ that might result from this change.
I had a discussion with a colleague who doesn’t think it should have any undesired consequence as it just add an extra view/functionnality to the portal, and wouldn’t change the process themselves, but a solution to test things out could be to use a test account
Setting up ABM will add additional properties and create a target accounts index page - these are the things that can’t be undone, but they shouldn’t impact any of your existing automation or efforts, only in that you might have to make updates to reflect your new processes.
@robertkreisler that’s a really good question and I’ll second the insight from @Jnix284 (that’s a great KB resource). While it sounds scary, it’s not. Activating the target account/ABM tools doesn’t erase anything you’ve done. It doesn’t limit workflows. It all adds to your efforts without changing what you currently have. You’ll be able to add workflows for assigning tiers based of revenue and other factors, for example.
So no, it doesn’t affect or limit what you’ve already built. I’ve turned these on for many portals and had more power, not less. You can breathe easy.
I also second what @danmoyle and @robertkreisler say about activating the ABM functionnality : no undesired side effects, you’re simply adding more juice to HubSpot and more to work with.
I guess the only reason why you can’t go back is that it’s creating new tables and relations in your instance’s database. I have a client who tried it out but simply did not keep using it.
The properties are just left alone and that client uses their account as a regular, non-ABMed account.
