# HubSpot & Microsoft Suite integration – tools comparison **URL:** \ **Category:** APIs & Integrations\ **Tags:** developer-tools\ **Created:** [May 11, 2022, 3:27pm UTC](https://community.hubspot.com/t/hubspot-microsoft-suite-integration-tools-comparison/56732 "2022-05-11T15:27:44Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![JColban](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jcolban/32/67037_2.png) [@JColban](https://community.hubspot.com/u/JColban)\ **Post date:** [May 11, 2022, 3:27pm UTC](https://community.hubspot.com/t/hubspot-microsoft-suite-integration-tools-comparison/56732/1 "2022-05-11T15:27:44Z")
Hello dear HubSpot community, We have acquired a yound company that uses HubSpot CRM and now we need to integrate it with our own Microsoft suite and database. Now, we ourselves have been using [Jitterbit](https://www.jitterbit.com/) for integration purposes for quite a while. Our latest acquisition came with another ipaas, namely [elastic.io](https://www.elastic.io/), and after playing with it for a few weeks to see how it would work for Hubspot-Microsoft integration, I kinda started liking it more and more and would like to propose to our management that we evaulate the tool for a complete switch. However, I would really appreciate if anyone could share their experience with [elastic.io](http://elastic.io); particularly vs Jitterbit if possible: - How does it work for you? - Have you run into any complications after increasing the number of integration jobs? - Are there any technology stack concerns you’d flag? Really anything would help me with my considerations. Thank you in advance! ---
**Author:** ![dennisedson](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/dennisedson/32/28044_2.png) [@dennisedson](https://community.hubspot.com/u/dennisedson)\ **Post date:** [May 12, 2022, 2:48pm UTC](https://community.hubspot.com/t/hubspot-microsoft-suite-integration-tools-comparison/56732/2 "2022-05-12T14:48:13Z")
@johnelmer , not sure if you have any thoughts on this or not, but thought I would throw you into the conversation even if you are kicking and screaming 🤣 ---
**Author:** ![johnelmer](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/johnelmer/32/55984_2.png) [@johnelmer](https://community.hubspot.com/u/johnelmer)\ **Post date:** [May 12, 2022, 3:30pm UTC](https://community.hubspot.com/t/hubspot-microsoft-suite-integration-tools-comparison/56732/3 "2022-05-12T15:30:45Z")
@JColban @dennisedson You have a wide array of options for integrating HubSpot and the Microsoft Dynamics applications. Here are a few points to consider: 1. The integration solution you choose should consider which applications you need to integrate, how you want the data to flow, and where the system of record will be kept. When you say Microsoft Suite, are you just talking about Office applications, Microsoft Dynamics CRM, or Dynamics ERPs? 2. According to their documentation, [Elastic.io](http://Elastic.io) only works with Contacts, Companies, Deals, Tickets, and Line Items. If you need to sync more objects, or custom objects, it won’t be a good long term solution. It looks like it won’t sync Engagements, which are usually extremely important for Marketing and Sales reporting. The decision on how to connect your systems should begin with a system architecture plan and an ERD. This will help you define functional requirements and identify tradeoffs so that you can make the best decision on the technology platform to use for the integration. Jitterbit and [Elastic.io](http://Elastic.io) are fundamentally different platforms, so this type of analysis is essential to success. ---
**Author:** ![Nagarjoon](https://avatars.discourse-cdn.com/v4/letter/n/e5b9ba/32.png) [@Nagarjoon](https://community.hubspot.com/u/Nagarjoon)\ **Post date:** [April 5, 2024, 3:08pm UTC](https://community.hubspot.com/t/hubspot-microsoft-suite-integration-tools-comparison/56732/4 "2024-04-05T15:08:13Z")
To effectively compare [elastic.io](http://elastic.io) with Jitterbit for your integration needs, consider the following: 1. **Performance and Reliability** : Evaluate how [elastic.io](http://elastic.io) performs compared to Jitterbit in terms of speed, reliability, and uptime. Look for any instances of downtime or sluggishness in data transfer. 2. **Scalability** : Assess how well [elastic.io](http://elastic.io) handles an increased number of integration jobs compared to Jitterbit. Look for any bottlenecks or limitations when scaling up the number of integrations. 3. **Ease of Use** : Determine the ease of use and user-friendliness of [elastic.io](http://elastic.io) compared to Jitterbit. Consider factors such as user interface intuitiveness, ease of setting up integrations, and learning curve for your team. 4. **Feature Set** : Compare the features offered by [elastic.io](http://elastic.io) and Jitterbit. Identify any key features that one platform offers and the other lacks, and determine which features are critical for your integration requirements. 5. **Technology Stack Compatibility** : Assess the compatibility of [elastic.io](http://elastic.io) and Jitterbit with your existing technology stack, including your Microsoft suite and database. Ensure that the chosen integration platform seamlessly integrates with your current infrastructure without causing any compatibility issues. 6. **Support and Documentation** : Evaluate the quality of support and documentation provided by [elastic.io](http://elastic.io) and Jitterbit. Consider factors such as response time for support inquiries, availability of resources such as tutorials and guides, and overall satisfaction with the level of support provided. Based on this assessment, you can make an informed recommendation to your management regarding whether to switch to [elastic.io](http://elastic.io) for your integration needs or continue using Jitterbit. Be sure to highlight any specific advantages or concerns identified during your evaluation process.