We just raised a $30M Series A: Read our story

Microsoft Exchange Competitors and Alternatives

Get our free report covering Zimbra, IceWarp, GFI, and other competitors of Microsoft Exchange. Updated: September 2021.
540,884 professionals have used our research since 2012.

Read reviews of Microsoft Exchange competitors and alternatives

NN
Technical Consultant at Hewlett Packard Enterprise Company
Real User
Top 5Leaderboard
Good query vault, scalable, stable, with quick responding support

Pros and Cons

  • "The archive allows the customers to search any items as far back as five or ten years ago."
  • "I cannot perform application backup, and I am not able to repair the license."

What is our primary use case?

I am not an end-user with this product. I'm a technical consultant.

I am responsible for the migration, as well as the upgrades of this product for my customers.

We use this solution in large enterprise companies, with several mailboxes, and are not able to go through the cloud, due to regulation or other similar reasons.

These companies need a reliable archive solution, and I always recommend Enterprise Vault.

How has it helped my organization?

This solution performs searches for items very quickly. 

Also, the mailboxes are very small in the on-premises locations. This reduces the time for the IT department for maintenance and improves performance on the Exchange server.

What is most valuable?

The most used feature of this solution is the search vault.

We have some customers who have many items in their mailbox. We want to provide them with a cache for two, three, or six months back.

The archive allows the customers to search any items as far back as five or ten years ago.

The search vault doesn't have the cache on Outlook and doesn't make it slower.

What needs improvement?

The backup area needs improvement. I cannot perform application backup, and I am not able to repair the license. 

If someone deletes an item from the vault server, I am not able to restore a single license. I would have to restore the complete mailbox and all of the partitions, which is a lot of work.

It is not a very good solution for the backup and restore capabilities.

For how long have I used the solution?

I have been working with this product for almost four years.

I try to keep the customers up-to-date. Almost all of my customers have the 12.4 or 12.5 version.

I do, however, have a customer who has an older version. But most are up-to-date.

What do I think about the stability of the solution?

The stability is great. This product is great.

We always have the systems on. I barely see any problems with this product. The issues are normally coming from the SQL server. Or, if the customer is not doing the maintenance.

The problems are from the SQL server, and not from the Enterprise Vault.

At times when there is an upgrade, we can experience a small issue.

What do I think about the scalability of the solution?

Scalability is huge. I archive billions of items with no issues at all. The search is great, especially with this newest version.

I don't have any issues with the scalability of this solution.

The size of the environments that we have deployed this solution to varies. We have customers with 15,000 users, some with 10,000 users and there are some with 100, and 500. The largest deployment is 15,000.

How are customer service and technical support?

Technical support is very fast. It's great. I always get my answer and I am always able to get an engineer to solve the issues.

One time, I had a case that took three months to fix tables in SQL and they did it. It was on the dark side, but they got the job done.

It took some time but it was resolved.

Which solution did I use previously and why did I switch?

I haven't had any clients who used another archive solution. They have exchanged on-premises but not to another archive.

How was the initial setup?

I was involved with the design. I installed the product. I upgrade the product and I migrate it to SQL. I do everything.

I start with the step-by-step rule task guide, follow the rule task requirements and the requirements for the SQL server. I install the product, create the policy for the clients, archive a couple of mailboxes to show the clients how is done. Once that is complete the customer takes the lead.

It can take a couple of days to deploy.

After the installation, the maintenance is a couple of hours a week, depending on the company, and how large they are. This does not require full-time work. A couple of times per week is sufficient.

What's my experience with pricing, setup cost, and licensing?

This is an area that is not relevant for me. I am not an end user or a buyer. I don't have this information.

Which other solutions did I evaluate?

Microsoft Exchange Archive is the largest, but I haven't used it. I always recommend Enterprise Vault because this is the main solution.

Microsoft has many solutions, but they don't work perfectly. It's not the best option.

What other advice do I have?

I recommend to my customers to open a new partition for every year or every six months.

It depends on the company and how many items they archive, how many mailboxes are archived, to keep the backup very fast. When I close the partition, I won't need to backup anymore. When it's closed, it is not changing.

There are many items, billions of them. To maintain, you can create a new partition every six months and back up a little bit more. The backup window is very convenient for the customer.

If you are on-premise and cannot go to the cloud, this is the best solution for easy maintenance of your Exchange server. You can go through many mailboxes with several items without a problem.

This product has done its job very well. I would rate Veritas Enterprise Vault a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
HD
Control Department Head of Information Security at a financial services firm with 1,001-5,000 employees
Real User
Top 5
It is light to manage and low-cost, but lacks storage management

Pros and Cons

  • "Zimbra Collaboration is light to manage. It works on the Linux operating system, which is far better to manage than Microsoft Windows. Microsoft Exchange works only on the Windows server. We prefer working on the Linux server for security reasons and ease of management. Zimbra Collaboration also has some integrated tools for security. It some modules to fight malware. These modules are not very powerful but are still doing a great job. Microsoft Exchange doesn't have a basic module. You have to purchase a security solution and add it to the solution. The cost of Zimbra Collaboration is one more reason for liking it. It is also very simple to migrate from Zimbra Collaboration to another email solution."
  • "Zimbra must improve its solution to make it easy so that the users don't have to use webmail to connect to their accounts and log in to webmail every time. This is something that is lacking in Zimbra Collaboration. They should provide a better way to easily connect email applications on the desktop to the Zimbra server. They should also try to have more functionality for storage management, like Microsoft Exchange. Currently, the management of the email data must be done manually in Zimbra Collaboration, which we are finding very difficult. They should provide a way to save emails so that you can have more space on the server and storage. Because of the lack of this functionality, we are planning to migrate to Microsoft Exchange. Microsoft Exchange provides a better way to manage storage than Zimbra Collaboration. You cannot have a mail solution without storage management because emails will always increase. Zimbra Collaboration also needs tools for management. More back-office tools are required to manage the whole mailbox and space. You don't only manage emails but also the documents attached to the emails. Therefore, you require tools to select and decide what do you want to save or how do you want to free up space in your infrastructure."

What is our primary use case?

We are mostly using Zimbra Collaboration for email purposes. It is also a collaborative tool. We also use it for sharing some documents and for meetings. 

What is most valuable?

Zimbra Collaboration is light to manage. It works on the Linux operating system, which is far better to manage than Microsoft Windows. Microsoft Exchange works only on the Windows server. We prefer working on the Linux server for security reasons and ease of management.

Zimbra Collaboration also has some integrated tools for security. It some modules to fight malware. These modules are not very powerful but are still doing a great job. Microsoft Exchange doesn't have a basic module. You have to purchase a security solution and add it to the solution. 

The cost of Zimbra Collaboration is one more reason for liking it. It is also very simple to migrate from Zimbra Collaboration to another email solution.

What needs improvement?

Zimbra must improve its solution to make it easy so that the users don't have to use webmail to connect to their accounts and log in to webmail every time. This is something that is lacking in Zimbra Collaboration. They should provide a better way to easily connect email applications on the desktop to the Zimbra server.

They should also try to have more functionality for storage management, like Microsoft Exchange. Currently, the management of the email data must be done manually in Zimbra Collaboration, which we are finding very difficult. They should provide a way to save emails so that you can have more space on the server and storage. Because of the lack of this functionality, we are planning to migrate to Microsoft Exchange. Microsoft Exchange provides a better way to manage storage than Zimbra Collaboration. You cannot have a mail solution without storage management because emails will always increase. 

Zimbra Collaboration also needs tools for management. More back-office tools are required to manage the whole mailbox and space. You don't only manage emails but also the documents attached to the emails. Therefore, you require tools to select and decide what do you want to save or how do you want to free up space in your infrastructure.

For how long have I used the solution?

I have been using Zimbra Collaboration for almost six years.

How are customer service and technical support?

Zimbra doesn't have good technical support. They are not always available for help, so we have to troubleshoot as much possible by ourselves. It is not easy to find help when we have any incidents.

We have a local partner who is an expert in Zimbra. They really help us by trying their best and doing what they can do. Zimbra support is not always available, so we work only with local support.

How was the initial setup?

Because Zimbra doesn't provide good support, it was difficult for our administration team to handle this solution in the beginning. They had to learn it on their own. The initial setup, however, wasn't really difficult. It was simple.

What about the implementation team?

The teams in charge installed it in a short time with the help of a partner.

What's my experience with pricing, setup cost, and licensing?

Zimbra Collaboration is less expensive than Microsoft Exchange. Zimbra works for small companies because it is not expensive. 

Zimbra Collaboration has more security tools than Microsoft Exchange. If you are choosing between Zimbra Collaboration and Microsoft Exchange, you have to take into account the cost of security tools with Microsoft Exchange. When you purchase Microsoft Exchange, you will also have to purchase tools for security, which adds to the cost. 

The migration from Zimbra Collaboration to another email solution is very simple and easy. Migration from Microsoft Exchange to another email solution is very difficult. Microsoft doesn't allow migration that easily. In fact, you have to pay for tools to do that. You have to buy some expensive tools to migrate.

What other advice do I have?

I would recommend this solution, but it depends on the size of the company and the cost. The number of emails that you use impacts the cost of the solution. 

For a small company, Zimbra Collaboration is good because it is simple, inexpensive, and not very difficult to deploy. For a big company, Microsoft Exchange is good because you have to manage the data, storage, and user emails, and you need a tool that can easily do it for you. Microsoft Exchange provides tools to manage the space and the server. You can create your own policy for emails. For example, you can save emails that are two years old somewhere else. Zimbra Collaboration currently does not have such functionality, and it is something very inconvenient because the emails keep on increasing, and the storage is not unlimited. Therefore, you have to find a way to manage the storage to save all emails and have free space for the new ones. This functionality is really powerful in Microsoft Exchange. That's why for a big company with 1,000 or more users, it's good to have Microsoft Exchange. It, however, also depends on your budget.

I would rate Zimbra Collaboration a seven out of ten. In spite of the lower cost of Zimbra Collaboration as compared to Microsoft Exchange, our management is planning to migrate to Microsoft Exchange because of the issue with storage management.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
MM
Senior Systems Tech/Admin at a computer software company with 1-10 employees
Reseller
Top 5
An easy implementation with a good user interface and pretty scalable

Pros and Cons

  • "The user interface is good."
  • "Most of our clients use Outlook and Kerio Connect. Occasionally, Kerio can be a bit slow. They could make it faster to get onto the web interface without so much load time. It's just slow with Outlook, however, for some reason."

What is our primary use case?

We primarily use the product as an integrated solution for our calendars and contacts and everything else. It's attached to our carrier operator.

What is most valuable?

It's a very healthy solution. It has a good survey or features that we like to use.

The user interface is good.

The implementation process isn't too complex.

What needs improvement?

We've been happy with the solution. It's worked for us so far so it's fine.

If they could integrate some sort of AI into the solution to make it more efficient, that would be interesting.

Most of our clients use Outlook and Kerio Connect. Occasionally, Kerio can be a bit slow. They could make it faster to get onto the web interface without so much load time. It's just slow with Outlook, however, for some reason.

For how long have I used the solution?

We've been using the solution since the product's inception. It's been about 15 years or so.

What do I think about the stability of the solution?

As long as the operating is stable, the Kerio connect will be very stable as well, so we don't have any problem with it. There aren't bugs and glitches. It doesn't crash or freeze. I consider it reliable.

What do I think about the scalability of the solution?

The solution can scale quite well. It can accommodate 10,000 depending on your hardware. It's quite robust.

It's a multi-domain solution. More than one company can be on the solution at one time.

We don't plan on increasing usage at this time.

How was the initial setup?

The solution's implementation is not complex in any way. It's pretty straightforward. We're using Linux systems to install it, however, we stay away from Window's services. That's a personal preference thing on our end.

We tend to maintain the solution for our clients. We have one person who handles maintenance and she's knowledgeable in everything from hardware to software to the operating system.

What about the implementation team?

We had help on the more technical details of the setup.

What's my experience with pricing, setup cost, and licensing?

The pricing is about $3 per mailbox per month.

What other advice do I have?

We have a mix of deployment models, beyond just the cloud.

If you're an admin, it's much preferable to use Kerio Connect because it's, easy to manage.

Overall, on a scale from one to ten, I'd rate the solution at and eight. There's no perfect system, however, this solution works quite well for us.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Abdulla Pathan
Technology Competency and Solution Head at LearningMate
Real User
Top 5Leaderboard
A stable and scalable solution for our emails, documents, and internal meetings

Pros and Cons

  • "It is quite a useful tool. It allows many people to work on a document. You can actually provide review comments and tag anybody to make the comment changes. You can also attach a document in Google Chat."
  • "We use Zoom most of the time for official meetings, and we use Google Meet only for internal meetings. I would like to get an improvised Google Meet. It would be good if they can make Google Meet more clear in communication and more scalable like Zoom."

What is our primary use case?

We are using the complete G Suite Enterprise. It includes Google Email, Google Drive, Google Meet, Google Docs, and Google Sites. For our internal meetings, we are using Google Meet. For our email services, Google Email is there, and for our documents, we use Google Drive Enterprise. We are using the latest version of G Suite Enterprise.

What is most valuable?

It is quite a useful tool. It allows many people to work on a document. You can actually provide review comments and tag anybody to make the comment changes. You can also attach a document in Google Chat.

What needs improvement?

We use Zoom most of the time for official meetings, and we use Google Meet only for internal meetings. I would like to get an improvised Google Meet. It would be good if they can make Google Meet more clear in communication and more scalable like Zoom.

For how long have I used the solution?

I have been using this solution for eight years.

What do I think about the stability of the solution?

It is stable.

What do I think about the scalability of the solution?

Being a cloud solution, it is very scalable. We have around 1,000 or 1,200 users.

How are customer service and technical support?

There is very little requirement for technical support because the solution is scalable and flexible. We don't really require any offline support from them except when there is a downtime.

Which solution did I use previously and why did I switch?

We were using our in-house exchange server for emails and document management. As we were growing, we needed a cloud-based solution.

How was the initial setup?

It is a cloud-based solution, so there is no on-premises installation.

What other advice do I have?

I would recommend G Suite for everybody. We plan to keep using this solution. 

I would rate G Suite Enterprise a ten out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Get our free report covering Zimbra, IceWarp, GFI, and other competitors of Microsoft Exchange. Updated: September 2021.
540,884 professionals have used our research since 2012.