How to switch form data submission from InfusionSoft to HubSpot integration

Other Questions HubSpot
1

I’m working on a form in my CMS application that currently sends data to InfusionSoft. Now I need to change it so it submits to HubSpot instead. I’ve been looking through the HubSpot API docs but can’t find clear examples of how to do this migration. Can someone point me in the right direction or share some code examples?

Here’s my current form model:

public class UserRegistrationHubspotModel {

    [StringLength(100), Required, Display(Name = "Name")]
    public string UserName { get; set; }

    [StringLength(100), Required, Display(Name = "Surname")]
    public string UserSurname { get; set; }

    [StringLength(75), Required, Display(Name = "Position")]
    public string Position { get; set; }

    [Display(Name = "hub_option_reports")]
    public bool Market_Reports { get; set; }

    [Display(Name = "hub_option_analytics")]
    public bool Data_Analytics { get; set; }

And here’s part of my controller that handles the submission:

[HttpPost, Themed]
public ActionResult ProcessRegistration(UserRegistrationModel userModel) {    
    //Prepare form data for submission
    NameValueCollection requestData = new NameValueCollection();
    requestData["inf_form_id"] = formId;
    requestData["inf_form_type"] = formType;
    requestData["infusion_ver"] = apiVersion;

What’s the best way to modify this to work with HubSpot’s API?

2

Went through this same transition last year - property mapping differences were the worst part. Your model looks like what I dealt with. HubSpot makes you create custom properties in their interface first before sending any data. You can’t just fire off random fields like InfusionSoft lets you. Those boolean fields (Market_Reports, Data_Analytics) need to be set up as custom contact properties in HubSpot’s settings first. Watch the rate limiting too - HubSpot’s way stricter than InfusionSoft on API calls per second. I had to build a queue system for bulk submissions because you’ll get errors if you hit their limits. Their response handling’s different too, so update your error handling logic.

3

just did this migration last month! HubSpot’s forms API is a lot cleaner than infusionsoft. You’ll need to move from NameValueCollection to a JSON payload and use their contacts API endpoint. Also, the property names aren’t the same - like ‘firstname’ instead of UserName. check out their c# SDK on nuget, makes it way easier!

4

You’ll need to ditch form submissions and switch to HubSpot’s Contacts API instead. I did this about 6 months ago - it’s a completely different beast. You’ll be making POST requests to their /contacts/v1/contact endpoint rather than submitting form data. Those boolean fields like Market_Reports? Map them to custom properties in HubSpot first, or they won’t work. Authentication’s different too - you need either an API key or OAuth token in the headers. Here’s the gotcha that tripped me up: HubSpot wants your data nested under a ‘properties’ object. Your JSON payload will look nothing like what you’re used to with InfusionSoft.