Celigo vs. HCL DataConnect

Celigo is great for transaction-based integrations (which is most), but not great for when you want to replicate data from one system to a database. For example, if you are trying to get all of your NetSuite data into a Snowflake database. However, if you are trying to get data out of NetSuite and create transactions in another system, it's perfect.

The choice to use Actian DataConnect really comes down to pricing and the type of integration project you are performing, specifically with the requirements, whether you want the integration to be on-premise or in the cloud, can you install agents on your servers etc. For integration tools it runs head to head with its competitors.

Incentivized

• Error handling
• Template handling
• Cost

Incentivized

• Map multiple source and destination tables - what would be done in many steps in SSIS can be done in one or two "maps" in Data Integrator.
• Platform independent, cloud based, no client software.
• Conversion of data types, write flat files - this helps us with integrating systems.
• Fairly straightforward to use if the user has ETL experience.

Incentivized

• AI would be amazing.
• Shorter wait for project kick-off.

Incentivized

• Integration Manager needs better scheduling improvements. Like dependencies, and not running a process again if the prior run is still running.
• New connector development does not seem a priority.

Incentivized

Had some rough patches in the beginning, but they were resolved.

Incentivized

Celigo handles errors much much better. Celigo stores templates all in one place making them much easier to find. Celigo interacts with your database as you are working allowing you to pull picklist values right from your db Celigo does not upsert large datasets as quickly and can take quite some time

Incentivized

Data Integrator was initially a part of a package deal for us with our new Student Information System. It was chosen prior to my arrival at the institution. Since I discovered we have SQL Server licenses, we have decided to use SSIS instead since I have a background in the MSBI stack and SSIS appears to be more straightforward (process flow philosophy vs "map" philosophy.)

Incentivized

• Adding additional sales channels for our eCommerce business which drove additional sales
• Real time inventory updates to website to limit overselling
• Operational efficiencies by no longer having to manually input data

• Our customer likes the consistent reliable integrations we have built so we [got] a definite return on investment.
• Problems are fairly easy to handle and rework.

Incentivized