The HubEngine is uncompromisingly built according to the no-coding principle. Synchronisation plans can be set up and controlled independently via the intuitive user interface. This basically works easily, quickly and without any programming knowledge. However, the duration of the set-up is largely dependent on the complexity of the project, i.e. the number of systems and endpoints to be connected.
Let’s assume that only two systems with only one endpoint each are to be synchronised bidirectionally. For example, this could be the profiles (API endpoint) from a marketing automation solution and the contacts (API endpoint) from a CRM system (see diagram). In this case, we need a HubEngine plan that connects the two endpoints and manages the data exchange, i.e. the synchronisation.
The time and effort required to set up the synchronisation via the HubEngine basically consists of the following tasks.
Tasks
- Detailed requirements – What exactly should be synchronised, when and how?
- Plan frequency – How often should synchronisation be executed, e.g. real time, every minute, every hour?
- Plan mappings for each direction – Which fields should be synchronised?
- Plan conditions for each direction – Which conditions per record must be fulfilled for synchronisation?
- Plan actions for each direction – Which actions should additionally be executed under which conditions?
- Plan implementation
- Debugging (testing)
- Plan activation (with release process if necessary)
Estimating the time and costs required for all tasks is not easy, as in practice the complete and detailed requirements only become clear during implementation. However, we have derived a non-binding rule of thumb for calculating the effort over a large number of projects, taking into account coordination, set-up and testing.
Rule of thumb for time estimation
- Uni-directional HubEngine plan with 25 fields: 4 hours
- Bi-directional HubEngine plan with 25 fields each: 8 hours
We are happy to proactively assist you with the set-up via our support. Together with you, we formulate the detailed requirements, such as the mapping or the frequency, and implement the logic.