> For the complete documentation index, see [llms.txt](https://docs.movebot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.movebot.io/features/calendar-migrations-with-movebot.md).

# Calendar Migrations with Movebot

Learn about calendar migrations with Movebot

## Introduction

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](/features/data-migrations-with-movebot.md) as a precursor to reading this.

#### **Supported Systems:**

* [Google Workspaces Gmail](/connections/google-workspaces-gmail.md)
* [Outlook Online (Office 365) EWS](/connections/outlook-online-office-365-ews.md)
* [Exchange Server](/connections/exchange-server.md)

## Quick Start Guide

Because transferring or migrating calendar data uses the same process as emails and contacts, simply follow the existing guide for [Mail Migrations](/features/mail-migrations-with-movebot.md).

### Enable Calendar Migration

1. When setting up or modifying a project, go to → Options. 
2. Enable the checkbox for "**Include Calendars**"
3. Your project is now configured for calendars and calendar-specific settings will appear

### Configure Attendee Mappings

Attendee Mappings control how participants are added to calendar events. To configure a mapping, select an email address from the source to map to the destination. The destination email address will then be the user added to the calendar event. 

You must configure Attendee Mappings for every calendar migration. The option appears in **Project Settings** after you enable calendar migration.

#### Using automated recommended mappings for attendees 

Movebot can compare the source and destination and automatically suggest user-to-user mappings based on the email address e.g. **<user1@oldomain.com> > <user1@domain2.newdomain.com>** . This can greatly speed up the attendee mapping process by pre-filling users automatically.

{% hint style="danger" %}
In order for Recommended Mappings to work, you ***must*** have users created in the destination. If not, we recommended creating the users before continuing the project setup to simplify the mapping process.&#x20;
{% endhint %}

Movebot will detect all users with similar names and create recommended mappings based on the users it finds. These mappings will be in pending state until you confirm, change, or ignore the recommendation.

Before applying the recommendations, check all pending mappings. The status icon indicates how the user will migrate with the current mapping.&#x20;

* **Green mappings** apply as `Source Mailbox → Destination Mailbox`. Green-mapped users appear on migrated events with their **new email address.**
* **Orange mappings** apply as `Source Mailbox → Source Mailbox`. Orange-mapped users **retain their source email address**, e.g. old or non migrating users.&#x20;
* External users do not require a mapping. Movebot migrates these attendees unchanged.

After adjusting and confirming that all mappings are correct, select **Add Recommended Mappings** to move the recommendations to Applied Mappings that will be used in the migration.&#x20;

#### Manually mapping attendees

Another option for mapping attendees is to create the mappings manually. You can do this by uploading a CSV using the mapping template or by using wildcards as shown below.&#x20;

#### Mappings with wildcard examples

| Scenario                           | Source Mapping            | Destination Mapping   |
| ---------------------------------- | ------------------------- | --------------------- |
| Same Domain and Username           | \*@domain.com             | \*@domain.com         |
| Domain Change (Username Unchanged) | \*@old-domain.com         | \*@new-domain.com     |
| Domain and Username Change         | <john.doe@old-domain.com> | <jdoe@new-domain.com> |

#### Advanced Calendar Settings

Advanced settings change what kind of data Movebot includes and how events and invitations are handled.&#x20;

{% hint style="danger" %}
These settings should not be adjusted unless explicitly instructed by our support staff.
{% endhint %}

| Setting                                      | Description                                                                                | Default  |
| -------------------------------------------- | ------------------------------------------------------------------------------------------ | -------- |
| Include External Events                      | Copy events where the migrating user was an attendee (but not the owner).                  | Enabled  |
| Send Invitations to Attendees                | Sends calendar invites to destination users after migration.                               | Disabled |
| Include External Shared Calendars            | Copies shared calendars as static snapshots. Does not preserve live sharing functionality. | Disabled |
| Ignore Events Older Than 7 Days (**legacy**) | Limits migration to only recent events.                                                    | Disabled |