TrustRadius: an HG Insights company

Jitterbit Manufacturing Reviews & Insights

Score7 out of 10

44 Reviews and Ratings

Community insights

TrustRadius Insights for Jitterbit are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Versatile Data Integration: Users have found Jitterbit to be a highly versatile tool for data loading, mapping, and integration between different systems. Several reviewers mentioned that it allowed them to streamline their data processes without the need for coding, making it much easier to manage and connect SalesForce and NetSuite.

Configurable Logging and Notifications: The configurable logging feature in Jitterbit has been highly valued by users. Many reviewers have mentioned that it provides clear visibility of the progress and any potential issues in running jobs. Additionally, the ability to receive notifications online or via email has helped users stay informed even when they are not actively monitoring the system.

User-Friendly Interface: Reviewers appreciate Jitterbit's user-friendly interface compared to other similar products. Multiple users have stated that it does not require developer skills to utilize its capabilities effectively, empowering non-technical users to take ownership of the integration process. This ease-of-use aspect is seen as a significant advantage by many customers.

Jitterbit Reviews

5 Reviews
ManufacturingChemicals1Furniture1Industrial Automation1Consumer Goods2

Jitterbit - Jack of all Trades, Master of ETL

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

We have 15 Jitterbit projects in production right now (housing about 5 times as many jobs/operations that run at various times of the day/night) and QA/DEV environments that mirror those projects. Currently, these jobs primarily move business data to and from our Salesforce org. We are currently also looking at Jitterbit's API creation and management capabilities for real-time data needs, but have not put anything info production yet... only QA.

Integrations we currently have (Source/Targets):
Oracle ↔️ Salesforce
SQL ↔️ Salesforce
FTP ↔️ Salesforce
Salesforce ↔️ Salesforce
Local File ↔️ Salesforce (Used in Jitterbit Cloud Dataloader for one time import/exports)

Jitterbit Features we Use: *Including, but not limited to the list below*
Operation Chaining
Email Notifications (success or failure)
Logging (WriteToOperationLog)
Scripting
Operation Chunking
Project Variables for source/target credentials
Conditional Mapping
StringToHex/Base64Decode for creation of varBinary SQL data
Get/Set Last Run Time – for pulling only modified records since last successful run
SQL Target Db Pre-script - Include Null Updates
Temporary Storage (for csv files to use further down Operation chain)


Pros

  • Logging - totally configurable by the user, you can log any details about your running jobs, online (WriteToOperationLog) or to an email.
  • Cloud management environment. Can manage users and/or the running of operations from the website and do not need a client application to do so.
  • Client application is full featured and allows for greater control than our last "EDI"-type product we owned.
  • Operation-chaining -- a necessity! And it works well.

Cons

  • 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.

Likelihood to Recommend

Salesforce ETL needs, DB-to-DB ETL needs, RESTful API needs, etc.

Great way to integrated Cloud-to-Cloud or Cloud-to-Onprem

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

We use Jitterbit to sync cloud systems to on-premise systems in a bi-directional way. Specifically, we link Salesforce and Great Plains by integrating Sales Orders, Purchase Orders, and inventory transactions. We also use Jitterbit to connect cloud systems -- specifically, our eCommerce site (Magento and Spree Commerce) with Salesforce around Sales Orders, Shipping Confirmations and Inventory.

Pros

  • Easy to connect systems without the use of developers
  • Provides a single management interface for all integrations
  • Highly stable and reliable

Cons

  • Some of the more advanced transformation possibilities aren't exactly clear without a lot of digging. Very basic connections (e.g. map this field to this field) along with basic transformation scripts (e.g. multiply X * Y) are super easy. But I know there are a ton more features and functionality that I feel is somewhat buried in the product

Likelihood to Recommend

If Jitterbit offers a connector for the endpoint (and it's constantly adding new connectors) then the integration is super easy and can be implemented at very low cost...possibly by in-house IT resources with no developers/specialists. Jitterbit also offers the ability to connect to more generic web SOAP services and API endpoints -- these connections require a little more technical knowledge, but are also very straightforward to set up. Jitterbit can also expose all of the transform operations as its own API endpoint. So if there's a need to execute one of the Jitterbit operations from a foreign system (web site, mobile app, or other systems) it's really easy to expose it as an API endpoint, essentially offering the ability to host an internal or external facing web service for anything that lives within Jitterbit.
Vetted Review
Jitterbit
3 years of experience

Great tool that will have your data in the cloud within minutes.

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

We have always used Informatica for our data integrations—first the on-prem version for many years and recently branching out into the Cloud version as we began our journey into a Salesforce rollout. It became clear to us IICS was not the right tool for the job with Salesforce or any of our SaaS integrations, so we experimented with Mulesoft and Jitterbit. Over the last year, we have become mostly a Mulesoft shop now, with some of our smaller and less supported apps still leveraging Jitterbit. I would say we are 20% Informatica Power Center, 60% Mulesoft and 20% Jitterbit. Currently, Jitterbit is only used for the smallest portion of our Salesforce integrations, shuttling data back and forth between our internal legacy CRM system and the external Salesforce cloud.

Pros

  • Some of the pieces we wanted to bring into Salesforce were quite complex, but Jitterbit handled it easily. It’s like it learns from past experiences and you benefit from someone, somewhere having gone through this before.
  • Easy to set up and get going from the start. It was only a few minutes after going through the set-up process that we were able to migrate data over from our internal system to the cloud.
  • Planning ahead for some of our AI-driven analytics, I think Jitterbit should be able to handle those well, it’s got a nice interface that walks us through what we need, as long as you are starting from a position of knowledge before attempting it.

Cons

  • There is a bit of a different look and feel to Jitterbit than the other ETL packages we were used to. Not bad different, but took just a little getting used to.
  • Pricing was higher than some of the other ETL tools we looked at, and we could not really understand why. It has the same ups and downs that any other tool has, so it wasn’t a complete package to give you a one-stop-shop, so we could not see why you would pay more for the tool over others in its class.
  • The connections were a little less than spectacular when comparing against Mulesoft. Sometimes you need a little more flexibility and we found it harder to be flexible with Jitterbit than other tools.

Likelihood to Recommend

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.
Vetted Review
Jitterbit
1 year of experience

Jitterbit from Manual to Automatic

Rating: 8 out of 10
Incentivized

Use Cases and Deployment Scope

It is being used by out Engineering department to push data from Fusion Life Cycle to Netsuite.

Pros

  • Automating the push of data has been a Godsend -- We were doing this entire process manually
  • Adding or making a edit has been a fairly easy process
  • The time it has saved us allowed us to not hire another person

Cons

  • Would be nice to see more examples how to do some things -- Would like to see how to go from Netsuite Data base to Excel.

Likelihood to Recommend

If you are having to do manual work for this type of process this is the only way to go
Vetted Review
Jitterbit
1 year of experience

Jittery

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

We are using Jitterbit to Integrate our ERP (JD Edwards) with our CRM - Salesforce.

Pros

  • Ease of use.
  • Flexibility to code.
  • Administration, logging and publishing code.

Cons

  • It can integrate with DB and other third party apps well, but it would be nice if we could also invoke existing processes / code (Like SSIS etc) from Jitterbit.
  • Would be nice if Jitterbit could also implement JD Edwards API to invoke business logic within JDE.

Likelihood to Recommend

Scalability - Jitterbit supports many different types of integration including SFTP, i.e. it can also be used as an EDI tool for ERP applications.