Reviews (1-24 of 24)
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*
Email Notifications (success or failure)
Project Variables for source/target credentials
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)
- 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.
- 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.
- Ease of use - while being more technical is useful, you don't need to be a developer to use many of JItterbit's capabilities
- Customer Support - we have always had great responsiveness to any questions or issues encountered
- Reliability - Jitterbit has been extremely reliable with no major outages in the recent past
- Integration recipes for more platforms - e.g. JIRA
- Fewer upgrades - there are upgrades every couple of weeks so if you are not using the cloud version, you need to manually "keep up"
Jitterbit helps us complete our complete solution delivery with their ability to integrate with various systems (cloud or on-premise), databases and machines. Their strong Salesforce integration capabilities and easy to use wizards are key when implementing Salesforce solutions.
- Built-in Salesforce wizard - for Salesforce projects, the wizard enables you to achieve the basic integration structure with easy to use wizards for all DML operations: Query, Upsert, Insert, Update and Delete.
- Scripting - when you need something more complex in your integrations, the script option will give you extended capabilities to handle those tough spots with a lot of built-in functions.
- Migration - while doing migrations is usually hard and painful, Jitterbit migrations are simple and fast. Using their migration tool, going from Dev -> QA -> Prod is a very simple process.
- Debug - integration can get complicated and sometimes strong debug capabilities are needed. adding checkpoints to track variables and a debugger can be big improvement.
- Logging can be improved, adding rich text options and other logging formats can assist when reviewing integration after run time.
- Version control - they should have the option to hold revisions on any object.
- 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.
- 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.
- Easy to connect systems without the use of developers
- Provides a single management interface for all integrations
- Highly stable and reliable
- 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
- Using Jitterbit with multiple Salesforce orgs. If you have to load/query into more than one org, the ability to save your connection information and easily switch between connections is a huge time saver. You can also access the same files for multiple orgs as needed.
- It took a little while to get used to remapping fields. Once you get the hang of the refreshing and remapping it works very well, but there was a bit of a learning curve to it.
- Some of the UI interactions aren't super intuitive. Closing tabs or getting to the right one can be a little difficult at times.
- Data Transformation - updating multiple sources to use our data dictionary
- Picking up files from our sftp site - removes manual intervention
- Move data from one org to another through Salesforce
- It was difficult to figure out how to export file sources
- We have to pay per integration site so that can be costly if we are using it for multiple sources
- Some of the icons are difficult to determine their functionality
Jitterbit Review: "Great program that is easy to use and free for data integrations with Salesforce"
- 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.
- It's not very easy to create backups of your field mappings so if you break something you can't just "rewind" the clock and unbreak it. The paid version offers a backup feature but even that is not super user-friendly.
- Larger companies probably don't have much use for this. I'm at a much larger company now and we handle such system integrations with more advanced tools.
- Sometimes we've had downtime from Jitterbit just due to the nature that it has to be hosted on a remote server. Our server was aging and had down times which affected Jitterbit.
If you're a larger company needing more complex integrations where extremely high reliability is needed and any downtime means revenue loss, you probably already have a different product in mind. Then again, you probably have an entire team that handles integrations and a data warehouse to support it!
- 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
- 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.
- Viewing data mappings
- Having lists of historic maps
- Getting granular in the way you update records
- It can't handle some characters like : ; ) etc., in the field name which is really annoying as you don't realise it until you try to run the load.
- Sometimes the process can be flaky and just not work for any good reason but that is rare.
- Preserves mappings so that you don't have to redo them. This was my biggest frustration with Salesforce's Apex Data Loader. I believe they may have added this functionality now but Jitterbit does this well and I'm not interested in switching back.
- Platform independence: I recently had a customer that required consultants to use MacBook Pros. My company laptop is a PC. Since Jitterbit is cloud-based, I was able to create mappings on one computer and execute them on the other.
- Ease of use: Jitterbit is simple to use and has a very intuitive interface. It auto-creates log files so that you can review the results of your data operations.
- One recent complaint is that I kept getting prompted in the application to upgrade but when I clicked the upgrade button I received a cryptic error. It didn't seem to affect the application fortunately. This occurred on both the Mac and PC versions.
- Ease of use.
- Flexibility to code.
- Administration, logging and publishing code.
- 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.
- Loading data
- The ability to easily change, map or upsert to and from SalesForce and NetSuite.
- Creating an Endpoint Web Service without writing any code.
- I only see a few drawbacks with Jitterbit but every time I see one they are already in the process of fixing this.
- We ran into an issue where were were doing and If Else loop query in salesforce that was using thousands of API request during the operation and they were already working on a Map Cache for this problem.
- Back when we first started working with JitterBit we had an issue of connecting to NetSuite but since then they have built connectors for NetSuite using their built in WSDLs
- Great for endpoint to endpoint integration where data transformation is an important component of the process.
- Visual nature of the mapping is very good and the general visual layout of the processes employing these mappings is also very good.
- Copying of process and mappings make the integration a lot easier than it would otherwise be.
- Scripting language takes some getting used to depending on your programming background.
- There is a lack of some standard template procedures that could be used to create variations from the template. This would be very beneficial.
- Logging utility needs a re-write since the filtering is not very intuitive and sometimes is not very effective.
- Mapping spreadsheet columns to object fields is very intuitive and easy to figure out
- Very speedy, considering the amount of information I am inputting. Pushes a list of failures with detailed reasons, which allows me to go back and fix as needed
- I felt extremely comfortable using the software within about 2 days... It was very easy to learn
- Infinitely easier to understand than the stock Salesforce data loader
- Mapping fields could provide a link to explain what the field is in more detail
- Hard to visualize the impact that your mapping will have, might be helpful to load in object IDs and lay out the old value and what the new value stands to be
- The time to transfer millions of rows from China or South Africa was remarkable, it was very quick.
- We never dropped rows or lost data.
- It was very easy to pick up and learn how to do a simple data transfer.
- Since I was grabbing data from seven identical systems, I would prefer that I could copy and paste an operation and just change the connection. Instead, I had to remap every transformation I made. Still, it was a time saver to be able to copy it.
- I wish the programming of more complex transformations were less code-based and more GUI-based. Without knowing java syntax it made even some simple transformations difficult.
- It was too easy to overwrite other developers code. A merge feature would have come in handy more than once.
- It handles different sources very efficiently.
- Programming in Jitterbit and the available plugins is simple and very effective.
- User administration permissions provisioning is easy.
- I would expect more math functions to be added as we had few issues while rounding the numbers.
- Currently I believe the rows are getting processed one by one, it would be beneficial if we could do a bulk insert options into SQL too.
- Jitterbit makes it easy to visualize the process flow of operations that it participates in.
- Once configured correctly Jitterbit runs reliably without much maintenance attention required.
- Jitterbit support has been responsive when we've needed to engage them for assistance.
- Setting up secured connections for web services required tweaking multiple application configuration files and custom code to get the support that we needed.
- The proprietary scripting language is relatively capable for data transformation, but could be improved to handle more complex scenarios. Presently, anything outside it's capability requires a custom Java plugin to be written.
- Jitterbit's mapping tool is fairly powerful, but entering a large amount of field information for data mapping and transformation can be time consuming and cumbersome.
- I feel like the documentation for advanced users is inadequate and I was forced to open support cases to ask questions, for which answers should be available online.
- Our implementations required developer-level skills including a good working knowledge of XML and XML Style Sheets.
I did work closely with the Jitterbit support team . They are very helpful and prompt.
- Good support team
- Does not use complicated code
- Users can easily understand the structure
- Need better performance with SFDC cloud
- Need to have a better process aligned
- Need to improve the log so that it is self ecplanatory to troubleshooting an issue
Jitterbit Scorecard Summary
Feature Scorecard Summary
We offer flexible pricing options to suit your needs. Contact 1.877.852.3500 for details.
Jitterbit Technical Details