Finance is one area where Sage 300 can help your business grow faster and get paid earlier. Sage offers multiple products under its domain dedicated to different business sections, such as;
HubSpot does offer a native integration option for some of the Sage products. The green-marked Sage products are available for native integration. The red-marked Sage 300 is not available for native integration; you have to follow the custom integration route.
Our client is a fan of both Sage 300 and HubSpot. They used Sage 300 for their business management and HubSpot for their marketing and lead generation. These two worked so well for our client's business that now they just wanted these tools to get married to sync their business operations and marketing for the better.
The goal was to transfer the data from Sage 300 to HubSpot for the marketing department to use it. The data set includes contacts, companies, sales orders, purchase orders, and product information.
Marketing Magicians at our client's company knew how to use these data sets to target their audience better in the marketing campaigns. They were already manually transferring the data from Sage 300 to HubSpot. Now, they want the process to be automated.
Computan comes to the scene and gives the magic wand to our client in the form of middleware. Middleware was developed using SQL database, which was used to save data from Sage 300. Within the middleware, another database was used to translate the data into the language HubSpot could understand. The below diagram will help you understand it better.
Every new data entry in Sage 300 would be entered in the first database in middleware and then the new custom-built database, from where it gets transferred in HubSpot using .NET applications and API Keys.
The frontend object names were distinct from the backend object names. 'S0102', for instance, was the backend name for 'emails,' which is the object name at the frontend. This was the way each field was named. As a result, our integration developers needed help to distinguish between the various fields on the backend. Developers sometimes asked the client to put testing content on the front end so they could see where it would go in the back end. They established the connection between the frontend's right fields and the backend in this manner.
All of the data fields in Sage are related to each other, so they must all be displayed in the same way in HubSpot.
A contact and company information is also linked to a purchase order when one is placed. The company is associated with contacts. Multiple lines of orders made up one sale order, such as five mobile phones, three tablets, and two laptops ordered together. It was necessary to update whether or not they had been invoiced. The sales order also listed the price of each product.
The Sage database stores a complicated string of data that needs to be sent to HubSpot in a precise relational order.
In Sage, the objects are interconnected, and once they are transferred to HubSpot, the same object relation must also exist.
The Computan developers implemented a one-way Sage 300 and HubSpot integration. Sage 300 is a desktop application, not a web application, so even if there had been a request for a two-way integration, it would not have been possible. There were no web APIs available to enable the two-way integration.
The two-way integration was held as the scope for the future. Whenever Sage 300 introduces its web application, we will introduce two-way integration.
This integration requires around 200 hours
.NET team lead Abdul Khaliq
Associate Software Engineer, Danyal
