A Message From Binary Tree’s Co-CEO, Steven PivnikDecember 10, 2010
Welcome to Binary Tree’s new blog. As Binary Tree’s Co-CEO and one of its founding members, this is an especially exciting moment for me. I’m proud to be the first person to post on Binary Tree’s new blog, Good Migrations. We want this blog to serve as another important way for Binary Tree to maintain open discussions and dialogue with our customers, partners, and anyone else who shares an active interest in email and application migration and business continuity solutions.
Binary Tree was established in 1993, primarily as an IT Services company specializing in custom application development. Our forte at the time wasMicrosoft FoxPro and integration work with legacy systems. The first large account that we landed was American Express. Amex was a large Lotus Notes shop and we soon started doing integration and development work between the two and other backend systems. We truly embraced the Notes platform and its capabilities and over the next two years, built up our name and image in the Lotus community.
Thanks to our growing reputation in the Lotus space and our experience as a development organization, JP Morgan hired us for a custom consulting project. JP Morgan ran Microsoft Mail on Apple Macs as one of their corporate messaging systems. They were standardizing on Lotus Notes and needed a conversion utility created to migrate users’ mail data to their new Notes platform from MS Mail. We developed a solution with two main components: export & import. Data was exported from MS Mail to the file system using HyperCard scripts and was then imported into Notes using Lotus Script. The solution worked great and was used to migrate thousands of users.
A month later, and to meet the requirements of Rockwell International, we also created a version of the tool to support MS Mail for Windows. Following that, we were contacted by a company running Groupwise that wanted to know if we could help them migrate to Lotus Notes. Since we already had the import mechanism written and proven, all we needed to do was write the export from Groupwise and we were done. This is how the tool set grew to eventually support two dozen mail and calendar solutions that were popular in the 1990’s. The tools were eventually merged into a single product called CMT for Notes. CMT stands for Complete Migration Technology.
In 1997, IBM licensed the product from us and shipped it worldwide with the Lotus Notes CDs. When new customers were deploying Notes and needed to migrate users and data from their existing system, they would run Binary Tree’s CMT product. This gave Binary Tree worldwide notoriety in the Lotus Notes space. Most of the customers who migrated to Lotus Notes in the 1990’s got there using Binary Tree’s software.
In the 2000 timeframe, these same customers started asking us if we also offered solutions to migrate from Lotus Notes to Microsoft Exchange. After saying no continuously (yet watching demand rise) we finally made the decision to support the Microsoft Platform as a target for migrations. We released our first migration tool to support Lotus Notes to Microsoft Exchange in late 2003/early 2004. The first release was named CMT Universal and has since been renamed CMT for Exchange. Even with a v1.0 product, customers selected us repeatedly worldwide as the migration provider of choice against more established competitors due to the relationship and trust we built up over the years with our customers.
Binary Tree has come a long way in the Microsoft space since the v1.0 release ofCMT for Exchange. An offering consisting of a single email migration tool has mushroomed into an entire suite of software products to help customers with the complex initiative of replacing a very sophisticated messaging and collaboration system. Our software has become synonymous with project planning, risk mitigation, and ensuring business continuity. The best example of the latter is our middleware product named CMT for Coexistence. This product allows for end users in a company going through a migration to be completely productive regardless of which side of the migration they’re on. It allows for mail to flow continuously and seamlessly, calendar functionality to work properly, and for workflow enabled applications to operate without requiring any remediation.
The robustness of our software suite and our track record in the migration field led Microsoft to select us as the premier provider of migration and coexistence software for customers moving to their Microsoft Online cloud offering namedBPOS (Business Productivity Online Services - recently renamed Office365). To date, Binary Tree software has been used to migrate more users to Microsoft Online than all other providers combined.
While we’ve been very busy growing migration market share, building aworldwide SI partner channel, and expanding into the European/Asia Pacific markets and , we’ve also been listening very closely to the rest of the messaging market, specifically, the customer segments still on Microsoft Exchange 2003. With the end of support near for 2003, customers will be looking to upgrade/migrate to Exchange 2010 in the very near future, either to on-premise implementations of Exchange, or to a cloud based solution. And even with cloud initiatives, there are choices between Microsoft hosted or partner hosted or private clouds.
These types of initiatives for organizations with more than 1,000 users are not a trivial task. Binary Tree’s answer to this challenge for customers on Exchange 2003 (or 2007) is our new offering named E2E Complete. With built in end user communications, migration scheduling and workload distribution, user list management, throughput estimation and black out window configuration, this product is already being touted as an Exchange administrator’s best friend for upgrades. We’re not fully sharing the product roadmap at this time, but suffice it to say, the solution will go from being a best friend, to a solution that anyone on Exchange can’t live without.
Wow …this sure is turning into quite a long introductory blog post, so I’ll wrap up with a these final words:
- Yesterday we were a household name for migrations to Lotus Notes.
- Today we are a household name for migrations from Lotus Notes to Microsoft Exchange.
- Tomorrow we will become a household name for the thousands of Exchange 2003 customers moving to 2010.
PS: Oh, wait did I mention there is still the day after tomorrow? I’ll just leave it at “SharePoint” for now