Calendar Migrations with Movebot
Learn about calendar migrations with Movebot
Last updated
Learn about calendar migrations with Movebot
Last updated
Movebot takes an unusual approach to calendar migrations, using the same mechanics of storage migrations for mail, calendar, and contacts. Because of this, we recommend that you read through Data Migrations with Movebot as a precursor to reading this.
Because transferring or migrating calendar data uses the same process as emails and contacts, simply follow the existing guide for
To begin transferring calendars, you need to enable calendars. You can do this by clicking on a project, navigating to settings, then content options. There you will see checkboxes to include calendars/contacts. Make sure these are checked to be able to move calendars/contacts.
If you enable calendars, some more options for migrating your calendar pop up.
Option | Description |
---|---|
Configure Event Attendee Mapping (Optional)
Transferring an event re-invites the current attendees on that event when it is created in the destination.
Configuring Events Attendee Mappings allows you to provide mappings for the attendee emails on those events, so that for example all emails ending in @movebot.io are mapped to @newmovebot.io in the destination, and event invites are sent there instead.
What properties get maintained when transferring a calendar event? - We aim to maintain as many properties on events as possible. These properties include the name, description, start/end times, recurrence information, attendees, the time the event was created & last updated, reminders, location, status, event type and original start time.
Source | Destination |
---|---|
Include External Events (Not Recommended)
This includes all events if checked, including events not owned by the user. Keeping this unchecked prevents event duplication
Include External/Shared Calendars (Not Recommended)
This includes all calendars if checked, including calendars not owned by the user. Keeping this unchecked prevents event duplication
Ignore Events Older than 7 days (Recommended)
This will ignore events that were created more than 7 days ago. This is typically preferred, to avoid moving old events. You can uncheck this box to include all events in the migration
*@google.com
*@microsoft.com
@google.com
@microsoft..com