Sumatra Development LLC

Newsflash: New trial of the server-side holiday insertion tool for 2013 for Exchange 2010 and Office 365. Click here.

The hard part in moving from Meeting Maker to Microsoft Exchange is getting all your crucial scheduling data out of Meeting Maker and into Exchange in one operation. For years this has been impossible.  We have developed the fast, reliable technology that allows you to preserve all of your meetings, activities, tasks, contacts and mission-critical scheduling information. We can convert multiple attached Meeting Maker servers, as well as work with you on a custom user mapping before moving to Exchange.

While some migration solutions work by moving many users at the client level, ours works by porting a Meeting Maker server directly into an Exchange 2007 server. 

BEFORE

AFTER

Does it work?  Yes. Just look at the screenshots above taken from a conversion. It's a custom, database-driven solution we've developed that gives you choice all along the way.  We've done migrations from Meeting Maker 5.5.x, 6.x, 7.x, and 8.x.  If you want to move to Exchange and take all your scheduling information along, contact us to arrange to see how.

What are your alternatives?  One company we saw ran both Meeting Maker and Exchange side-by-side for a week and had users type their own meetings back in.  Some users used Pilots to download their calendars and upload them to Outlook/Exchange.  They lost all live meeting information (attendees, attendee status, etc) and all recurring meetings were turned into multiple instances of single meetings.  They also lived through what one veteran of the process called "conference room anarchy."  Our solutions avoid these serious problems. 

Check out our guide: Eight Best Practices when Migrating Calendar Data.  It's meant for those of you evaluating different approaches.  We always encourage feedback.

How does this work?  In two phases.  Phase I involves extracting the Meeting Maker server data and putting it into a useful RDBMS form (usually MS Access, though it's simple for us to convert directly to SQL).  Phase II  takes our database and imports it into Exchange. Our Exchange 2010 insertion code uses Exchange Web Services (EWS). 

Also, while your migration is going on we are tracking transactions as we move your Meeting Maker data into Exchange.  This allows us to start and stop the process at will, back out if appropriate, and to produce accurate reports on what has happened on your Exchange server.

On average we convert one Meeting Maker server per week.  Since October, 2001, we have successfully migrated thousands of users, with more on the way.  Over a Memorial Day Weekend in we moved a 9900 user installation -- Meeting Maker's 3^rd largest installation ever.  Recently we converted a 9000+ user installation which was at the time their largest remaining.  We've converted data in North America, Australia, and Europe.  Whether your server is on Windows, Macintosh, or UNIX we can migrate it.  

When you're ready to make the switch contact us.