A common question we hear is “How to can I get contacts from one Infusionsoft account into another account”?
What most people don’t realize is that there is a built-in feature for this.
- WARNING: Using this feature to get contacts from one business to another business (where they have not opted in) is not a good idea. This will lead to a high spam complaint rate and will likely get your Infusionsoft account shut down. This feature should only be used to pass contacts from one account to another account being used by the same business where a contact has opted into marketing.
So, you have two Infusionsoft accounts. For the sake of simplicity, let’s call them the “sending” account and the “receiving” account.
STEP 1:
In the “sending” account, go to Admin -> Settings -> Relationships. Here you’ll add the account name (app name) and the API key, which you’ll need to get from the receiving account under Admin -> Settings -> Application -> Encrypted Key.
Step 2:
Once you save the relationship, go to Admin -> Settings -> Lead Distribution Rules. There you’ll give your new rule a name, determine the rule type, and then choose the relationship you set up in the previous step.
Under “Rule Type” it’s best to select to select “Always true”. You can determine when and how this happens in your Campaigns and or Action Sets.
Step 3:
In the “receiving” account, set up an Action Set to run when a new lead is passed over from the “sending” account. Go to CRM -> Settings -> Action Sets. Create a new Action Set and use it to apply a Trigger tag that starts a Sequence in a Campaign.
Note the ID of the Action Set. You can do that by looking at your list of Action Sets. Sort by ID so the highest ID (most recently created) is at the top. Get the ID of the Action Set you just created.
Step 4:
Go back into the “sending” account and create an Action Set there. In the Action Set, you only need one action “Distribute record to another Infusionsoft application”. Then select the relationship you set up and type in the Action Set ID from the “receiving” app that you set up.
NOTE: It is important to realize the following:
-
- Contacts will come over as “Marketable” by default. Even if they’re already opted out in the “sending” account. So, be careful not to email people who have opted out.
- As of the date of this blog post, the Action Set that should be run in the receiving account is not working. Contacts will come over, but the Action Set will not run.
- If a contact is sent to the “receiving” account, and then subsequently deleted from the “receiving” account, and then you try and pass it to the “receiving” account again, it will not work. It will only send new contacts. But it will not recreate contacts that have been deleted.
Thanks for the excellent article! Will this method also transfer along orders and invoices that belong to the transferred contacts?
Pep, this method will only bring over contact data. It will not bring over tags, orders, invoices, etc.
Tyler – good post. I set it up as outlined above but the contact is not showing up in my receiving app 🙁 Does it take some time or should it be pretty instant?
Hey Drew, it should be pretty instantaneous. Let me check and see if it’s still working. I wouldn’t be surprised if Infusionsoft discontinued this feature since a native Zapier integration is coming out.
thanks. let me know what you find out. hopefully I just did something wrong 😉
While Action Sets will not be triggered in the receiving application solely on the contact record coming in, you can utilize Admin -> Setting-> Application-> API -> Incoming Action Set to apply a tag to incoming contact records as the steps outlined in this article do rely on the API, you just don’t have to do or develop anything fancy because it’s already there 🙂
It is important to note that if you have contacts coming in via the API outside of this, you would want to explore the rules and functionality to see if you can accomplish your goals, as this is not something I have looked into tested with this functionality.
True, true. GREAT suggestion Brianna. I just tested it and it works great. Thanks!
If they have contacts coming in from other API’s that should not receive the same tag, how would I get around this?
Hey Drew, it seems to have worked fine for me.
ok let me start over and see if it works. to be clear, here’s what I tried.
opted into a form into sending app
and hoped to see the contact in the receiving app campaign
Make sure the form starts a sequence that contains a Legacy Action Set. That Action Set needs to run an action to “Distribute to another Infusionsoft application”.
turns out it is creating the contacts in the receiving app, but not applying the tags per the action set. IFS support says this is not possible … they say the opt in form needs to be on both apps, but I’m not sure that even makes sense???
They don’t know what they’re talking about. The action set part of this feature is broken.
Cheers Tyler. Really helpful dude.
When a contact comes into the Infusionsoft account via the action set, is there anything to check if the person already exists in the other app rather than create a duplicate account for said individual?