Jitterbit Harmony Platform alternatives and competitors

I integrate Salesforce and some other third-party cloud platforms including payroll and stuff like that. I'm pushing data and making updates.

The solution is an integration tool. Based on changes in one place, I'm pushing out integration to other places to make updates, et cetera. Overall, it is a robust platform.

I have found the solution to be scalable.

The stability is very good.

The product could be a little bit more user-friendly.

The company needs to offer better documentation.

The initial setup is complex. It is what it is. You have to deal with it.

There's something missing with Salesforce platform events that they supposedly support, however, it doesn't work well with their cloud platform. It would be nice if they would get that working normally. They say they support it, and yet, it just fires multiple times. It's not reliable. You can't use it. 

I've been using the solution for about two years at this point.

The solution is quite stable. I don't deal with bugs or glitches. It doesn't crash or freeze. It's reliable. 

The scalability capabilities are pretty good.

There aren't a lot of users that have access to the product directly. The solution is really cordoned off, meaning it's working based off of changes in the system. Everybody's using the system and making changes, and then the integration kick gets kicked off. Working on the platform, making changes, that's very minimal work and that's just me and someone else.

Currently, we're on a pretty steady path. I can't speak to if there are plans to increase usage.

I worked with people from their technical support on the initial onboarding. It's reasonable in terms of the amount of service they offer.

I did not previously use a different solution.

The initial setup is very complex. It's not simple or straightforward. 

I can't speak to how long deployment took, as it was handled by a third party.

There is just me and one other person that handles the maintenance aspect of the product.

I use third-party people to get me set up and build-out, and that's what I continue to do. These third parties aren't resellers. They are freelancers. 

The ROI flows. The integration is working. Our systems are able to talk to each other.

The cost of the solution is in the neighborhood of $20,000 annually. There are no costs above the standard licensing fee.

I did look at a few other options before choosing this product. I looked at Workado and Jitterbit.

I'm just a customer and an end-user.

I would advise potential new users that they need to have some deep expertise on the Boomi platform to be able to successfully do what they want to do with it.

Out of ten, I'd rate the solution at a seven. It does the job well and it's robust, however, it is needlessly overcomplicated, and the documentation could be better.

The primary use case of this solution is to extract ETLS, transform and load data, and organize database synchronization.

The most valuable feature of this solution is the data flow, which is the same SQL server in important service, integration services, which is a very robust and powerful tool to transform data.

The solution can be improved by decreasing the warmup time which currently can take up to five minutes.

I have been using the solution for two years.

The solution is extremely stable.

The solution is scalable.

Previously I used AWS Glue and SSIS.

The initial setup is straightforward.

The implementation was completed in-house and is immediate because it is a native cloud tool.

I have seen an ROI with the time saved migrating data for reports.

The solution's fees are based on a pay-per-minute use plus the amount of data required to process. The more data you process the more CPUs and time is required which increases the cost of using this solution.

I give the solution ten out of ten.

The only thing you need to deploy the solution is to click on publish.

The solution includes a feature that increases the number of processors used which makes it very powerful and adds to the scalability.

We have three people using the solution in our organization and one engineer that maintains it.

I recommend to any potential user to factor in the five-minute warm-up time that is required for each execution.