Jitterbit vs. TeamDynamix iPaaS

This is a great tool for bringing data out of your locked, internal systems and getting it into the cloud. It meshes well with Salesforce and is fairly easy to use, helping the transition from other older, more complex tools into a more modern environment. It has lots of competition in this space and some are better than others, but if your data is straight forward and you know it well, Jitterbit will get the job done. If you are not as close or comfortable with your data and need to do some wildly complex migrations, there might be better packages out there for you.

Incentivized

Its great for enhancing integration and automation capabilities. It has a relatively friendly interface, though needs some improvement. It can feel overwhelming at times. It empowers both IT and business leaders to drive digital transformation effectively.

• UI is super easy to understand with a low learning curve so admins can figure it out and maintain it without breaking anything.
• It's FREE! There's a paid version too but I like that you can use most of the features for free and they're not pushy with buying.
• There's a great user community that you can google and ask any questions. Most problems I've encountered have been posted and answered already.

Incentivized

• Makes development possible for those without code experience.
• Lays out options for the team to utilize.
• Provides a visual view of a flow for use.

Incentivized

• Migrating operations from QA to Production work well for initial deployment, however, when migrating an update to an existing job to production, sometimes certain project items are duplicated. This is not the end of the world... the duplicates can be removed, but would be nice if it was not required.
• I have not found a way to trap under-the-covers SOAP errors (for example, when a query you are running against Salesforce takes too long). You get a warning error in the operation log that the job only pulled a "partial" file, but it does not fail.

Incentivized

• More documentation for starters using iPaaS.
• Let us use our own HTML.
• Chat bot to ask questions while working in iPaaS.

I have been evaluating other tools as a continuous improvement practice. I would like something that would be easier to use for a non-technical user. I work for a small organization and have no back-up for Jitterbit if something happens to me. We don't have the technically savvy employees to understand it.

Intuitive "Pill-Based" Data Transformation: Moving and formatting data across disparate platforms has traditionally been a syntax headache. TeamDynamix simplifies this by utilizing selectable data "pills," allowing users to click and visually bind fields—such as stitching a "First Name" and "Last Name" payload together—in seconds.

They have some of the best support of any software vendor that we use. They always get our issues resolved quickly

Evaluated Dell Boomi and Celigo as alternatives prior to purchasing Jitterbit. We went with Jitterbit at that time because we could handle all changes ourselves without any assistance from Jitterbit, and we liked their size and nimbleness. Dell Boomi was too big for us, and Celigo at that time did not have a self-service model. Every change had to go through them (although that has since changed). We were not in a position to be able to wait for someone to make changes for us given the rate of change within the business.

Incentivized

Boomi is expensive, has limited connector licenses, and is harder to write an integration.

• The time it takes to connect systems has reduced by orders of magnitude. Previously, we would custom-develop connectors between various systems and they would all be managed by different vendors. With Jitterbit speed-to-deploy and the efficiency gained by managing all connections in one dashboard has been the greatest piece of the ROI.

Incentivized

• Save time on ticket response.
• Create automated and tailored responses to tickets.
• Gain insights and data on our device activation tickets (we found that 25% of our tickets are for a single ticket, and we created a better-worded KB to facilitate fixes).