Integration Hub vs custom connectors for ERP data sync: maintenance

BPM AgilePoint
, , , , , , , ,
1

We’re designing data synchronization between AgilePoint and our ERP system (SAP). The choice is between using Integration Hub with pre-built connectors versus developing custom connectors. I’d like to hear experiences from teams who’ve made this choice.

Integration Hub offers ready-made SAP connectors with built-in error handling and monitoring. The setup looks straightforward but I’m concerned about flexibility for our specific data mapping requirements. Custom connectors give us complete control over the integration logic but require more development effort.

Key considerations for our decision: Integration Hub maintenance overhead versus custom connector flexibility, how upgrades affect each approach, and long-term support implications. Our ERP integration needs to handle real-time order data, inventory updates, and customer master data sync.

What factors should weigh most heavily in this decision? Looking for real-world experiences with both approaches.

2

You can use a hybrid approach. Integration Hub connectors for basic CRUD operations and data retrieval, then add custom transformation logic in your AgilePoint process using custom activities or scripts. This gives you the maintenance benefits of managed connectors while keeping flexibility for complex transformations. We do this for several clients - the connector handles the API communication and authentication, while business logic lives in the process layer where it’s easier to maintain and test.

3

Our team built custom connectors for Oracle ERP integration. We needed very specific data transformations and business logic that the standard connectors couldn’t handle. The flexibility is great, but the maintenance cost is real. Every AgilePoint upgrade requires testing and sometimes refactoring our custom code. We also have to monitor SAP API changes ourselves. Budget about 15-20% ongoing maintenance effort for custom connectors.

4

After working with both approaches across multiple implementations, here’s my analysis of the key decision factors:

Integration Hub Maintenance: The maintenance advantage is substantial for standard integration scenarios. AgilePoint manages connector updates, security patches, and API compatibility. When ERP vendors release new API versions, Integration Hub connectors are updated centrally. You benefit from bug fixes and improvements without custom code changes. However, you’re dependent on AgilePoint’s update schedule - if your ERP makes breaking changes, you wait for AgilePoint to release an updated connector.

For your real-time order data and inventory sync use case, Integration Hub connectors handle the common patterns well. Error handling, retry logic, and monitoring are built-in. The maintenance overhead is approximately 5-10% compared to 15-20% for custom connectors.

Custom Connector Flexibility: Custom connectors give you complete control over integration logic, data transformations, and error handling. This flexibility is crucial when:

  • You have highly specialized data mapping requirements
  • Your ERP has custom APIs or extensions
  • You need integration patterns not supported by standard connectors
  • Performance optimization requires custom caching or batching logic

The development effort is higher initially (3-4 weeks vs 1-2 weeks for Integration Hub setup), and ongoing maintenance requires dedicated resources.

Upgrade and Support Considerations: Integration Hub upgrades are generally smoother because connector compatibility is tested by AgilePoint. Custom connectors require testing with every AgilePoint version upgrade and every ERP API change. Budget for regression testing and potential refactoring.

Support is another differentiator. Integration Hub issues are covered by AgilePoint support. Custom connector issues require your team’s expertise. If you lose the developer who built the connector, knowledge transfer becomes critical.

Recommendation for Your Scenario: For real-time order data, inventory updates, and customer master data sync with SAP, I’d recommend starting with Integration Hub connectors and adding custom transformation logic in the process layer (as Priya suggested). This hybrid approach gives you:

  • Managed connectivity and authentication (Integration Hub)
  • Flexibility for complex data transformations (custom activities in processes)
  • Lower maintenance burden overall
  • Easier upgrade path

Reserve custom connectors for scenarios where Integration Hub truly can’t meet the requirement - like proprietary SAP extensions or performance-critical bulk operations that need custom optimization.

The long-term total cost of ownership typically favors Integration Hub unless you have very specific requirements that demand custom development.