How Cloudiway Uses Microsoft Teams Import APIs
Leverage Microsoft Teams Import APIs for optimized throughput and metadata preservation when migrating from Slack or Microsoft Teams.
Overview
Cloudiway leverages Microsoft Teams Import APIs to optimize migration throughput when migrating from Slack and Microsoft Teams. This approach enables high-speed message migration with full metadata preservation.
High Performance
Thousands of messages per hour
Metadata Preserved
Creator and timestamp intact
Order Preserved
Messages in correct sequence
Five-Step Migration Process
Step 1: Create Team in Migration Mode
Teams must be created programmatically in Migration Mode to access the import functionality. This is handled automatically by Cloudiway when you run preprocessing.
What Happens
- Team is created with suffix
(Cloudiway Migration In-Progress) - Team is invisible to end users during migration
- Administrators can manage the team via Teams Admin Console
Automatic Activation
Running preprocessing in Cloudiway automatically initiates Migration Mode for newly created teams.
Existing Teams
When migrating to existing teams (not created through Cloudiway), the system automatically reverts to standard APIs, which have lower throughput.
Step 2: Create Channels in Migration Mode
Channels must be created within a Team that is already in Migration Mode. Cloudiway handles this automatically when prerequisites are met.
Requirements
- Parent team must be in Migration Mode
- Channel must be standard (not private) during creation
- Preprocessing completed successfully
Step 3: Import Messages
When both the Team and channel are in Migration Mode, running the migration activates the high-performance Import APIs.
Key Benefits of Import APIs
Performance
Throughput is significantly better than standard APIs, supporting thousands of messages per hour.
Metadata Preservation
Original creator and timestamp information is preserved for all messages.
Message Ordering
Teams automatically reorders messages to maintain correct chronological sequence.
Bulk Operations
Messages are processed in batches for optimal efficiency.
Step 4: Complete Team and Channel Migration
During this phase, you can run delta passes to migrate any new messages that were created since the initial migration. The system remains in import mode during delta passes.
Post Migration Job
The Post Migration Job finalizes the migration by:
- Closing teams and channels (removes Migration Mode)
- Removing the "(Cloudiway Migration In-Progress)" suffix
- Enabling member migration
- Handling private channels migration
Step 5: Add Team Members
Membership migration occurs only after teams are closed (no longer in Migration Mode). This ensures that users don't see incomplete teams during migration.
Migration Sequence
Private Channels
API Limitation
Microsoft Teams Import APIs do not support creating private channels in Migration Mode. Cloudiway handles this limitation automatically.
How Private Channels Are Handled
Private channel migration is delayed until the Post Migration Job executes after the team is closed:
- 1 Standard channels are migrated first using Import APIs
- 2 Team is closed (exits Migration Mode)
- 3 Private channels are created and migrated using standard APIs