Great way to integrated Cloud-to-Cloud or Cloud-to-Onprem
April 08, 2019
Great way to integrated Cloud-to-Cloud or Cloud-to-Onprem
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Jitterbit
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
- 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.
Jitterbit is completely cloud-based and offers a cleaner way to connect to SOAP API endpoints. SQL Server Integration Services has a larger ecosystem of plugin connectors by third parties (at a cost), but the downside is that you still need to use something like Visual Studio to design the integrations and they are executed on-premise via SQL Agent. Jitterbit also has a cleaner line of customer support vs. the Microsoft model which generally assumes you're working with a VAR. Setup and deployment with Jitterbit are easier and doesn't require as much knowledge of Active Directory / user security / etc.
Comments
Please log in to join the conversation