The danger of ignoring your calendars in a migration.
Your company selected Microsoft Exchange/Office365 to keep costs down and maintain employee productivity. Moving email inboxes is only part of your productivity problem when migrating into Exchange or Office 365. The other is moving your corporate calendars and preserving all the crucial guest lists, responses, resource and conference room bookings, and recurrence patterns. Sumatra Development’s migration technology allows you to do that.
Calendars and schedules are a critical component of your daily workflow, but are mostly neglected or given scant attention during a migration. Without correctly and accurately migrating calendars, employee productivity drops substantially post-migration. Sumatra’s solution minimizes this negative impact.
Watch our video on moving Oracle Beehive calendars, contacts, and tasks into Office 365. We can do the same with Meeting Maker, Oracle Calendar Server, and Zimbra. We can migrate Google Calendar into Exchange as well (but no enterprise has asked for it yet).
How much can you save?
If your Office 365-enabled employees are earning $100 an hour (on average) and it takes 2-3 hours to re-create their calendar (and do not forget the conference rooms and resources!) that is a productivity loss of $200-$300 PER PERSON. We have historically found this to be a conservative estimate. Multiply that by the number of users you’re migrating.
You will find this productivity loss whether you go cold turkey and require your users to re-input all their data, or use tools that handle a client side-import that puts events in, but does not preserve guests and responses. Our full-state process preserves the guests and responses keeping meetings as meetings.
Watch the video. See how effective it is to use Sumatra’s migration tools!
Then contact us to get started.
What are the advantages of the Sumatra process?
- Migrated calendars means users are immediately productive.
- No end-user actions required.
- No wasted time re-creating meetings. Especially true for the CxOs and their admins.
- No confusion over rooms and resources.
- Safety net for a clean “undo” should you need to rollback.
- Server-to-server, not client-to-client
- Process controlled by your own administrators.