Skip to main content

Hubspot + WeClapp Logo_Resized_Transparent

The best of both worlds

HubSpot CRM and WeClapp ERP



Challenges:

WeClapp ERP is deeply integrated into internal tools and processes. However, the WeClapp CRM functionalities for Sales and Service are not enough:

  • Low analysis capabilities of sales and service activities
  • Usage and acceptance are low due to user-unfriendly software and lead to a lack of controlling and poor quality assurance
  • The data quality is not dependable and sometimes leads to incorrect conclusions
  • No CMS automation is possible and there are high costs for workarounds


Goals:

  • WeClapp remains as ERP system, HubSpot is introduced as CRM
  • Synchronization of all contacts and offers (incl. products) from HubSpot to WeClapp
  • Sales team work now only takes place in HubSpot. Finance can continue to work in WeClapp
  • Taking the entire team and all relevant data with you for a smooth transition

The Project Set-up

From Workshop to Project Plan

The first major task of the project is to understand the client's internal processes.

The method of choice here is a joint workshop on imports and integrations. There are also separate workshops for sales and other teams. This leads to questions and answers on the following topics:

  • How is WeClapp integrated into the technical infrastructure?
  • Where can WeClapp be detached?
  • Which data must be transferred from HubSpot to WeClapp, when and how?
  • What data needs to be imported into HubSpot and how?


From the workshop, we can draw up a precise project plan in which all the threads come together at the end:

  • Consultation with Sales and other teams
  • Personalization of the HubSpot portal
  • HubSpot + WeClapp Integration
  • Data import from WeClapp to HubSpot
Product Management
Analytics

The Data Import to HubSpot

We use the following process for the conversion:

1. The Creation of a Mapping Document
This contains all the properties and objects that are transferred from the old CRM and the form in which they are imported into HubSpot. Desired data manipulations are also recorded in this document. This creates a clear and transparent work order.

2. Preparation of the Coded Script
Our scripts use either CSV exports or API interfaces. Scripts allow us to optimally prepare the export so that we only have to execute them before the final onboarding day.

3. The Test Import
To ensure that everything meshes as desired when importing the data to HubSpot, a test import is carried out in a HubSpot test environment beforehand. This allows all project participants to view and check the imported data in detail in HubSpot.

4. Final Data Import
In the last step, the final import is carried out on the evening before onboarding - the official start of the team in HubSpot. Due to the proximity in time, the most up-to-date data is imported from WeClapp. This increases the acceptance of HubSpot in the team.

The WeClapp Integration through HubSpot Workflows

The aim of the integration is to automatically transfer HubSpot offers to WeClapp after acceptance by the customer. There they are to be listed as orders, products are to be transferred and the corresponding contact is to be transferred from WeClapp.

As the existing native link between HubSpot and WeClapp does not do this, we rely on a workflow including custom code. The decisive factor here is the "HubSpot offer accepted" trigger required for the process. This triggers the workflow, the heart of which is a custom code element. In this case, a Python script that performs several API operations and transfers the order to WeClapp in the final step.

If the transfer was not successful, the HubSpot CRM manager will be notified. If the transfer is successful, some data is transferred to the corresponding HubSpot deal. This allows the correct transfer to be tracked directly in the deal pipeline.

Custom_code_Workflow

Successful Tool Migration

The solution using HubSpot Workflow and custom code is useful for several reasons:

1. No Agency Dependency
As there is no middleware that is located on an agency server, there is less agency dependency with this setup. In principle, anyone with the appropriate HubSpot rights and knowledge of Node.js or Python can reproduce and edit the interface. All non-custom code elements of the workflow can also be easily adapted by the internal CRM manager. This creates significantly more agility and update options.

2. More Transparency and Everything in One Location
Interface errors can be displayed directly in HubSpot. This leads to significantly more transparency as to which data was transferred and when, without having to log into a middleware tool.

3. Costs
The development costs are usually significantly lower than with middleware, Zapier or similar. There are also no additional server costs. Only HubSpot Operations Hub Professional is required, which is also equipped with other helpful features for HubSpot Super Admins.

Sebastian Schäfer made2GROW


This sounds interesting?

Do you have a similar case or want to find out whether HubSpot and custom code workflows could be something for you?

Get in touch with us for an initial, no-obligation discussion and we'll see together how you can generate new leads with HubSpot. In person in Cologne or digitally!

Thanks to our many years of experience as a HubSpot agency in many small and large projects, we will know which solution is right for your company. Book an appointment for a no-obligation discovery call and we'll see together whether and how you can become successful with HubSpot 🤓