Overview
Migrating direct messages between collaboration platforms like Microsoft Teams, Google Chat, and Slack presents unique challenges due to API limitations and platform-specific constraints. This article explains how Cloudiway handles chat migration and what to expect during the process.
Supported Migration Paths
- Google Chat to Microsoft Teams
- Slack to Microsoft Teams
- Teams tenant to Teams tenant
How It Works
Due to Microsoft Teams API restrictions, direct messages cannot be injected "as" the original sender. Understanding this constraint is essential for setting migration expectations.
Administrator Account Role
Messages are injected using the target connector's administrator account, which must have an Office 365 license that includes Teams access.
Important
Message Metadata Handling
While messages display the administrator's name as the sender with a migration-date timestamp, each message preserves the original context:
Here's the quarterly report we discussed in yesterday's meeting.
This dual-timestamp approach maintains historical context despite platform API constraints.
Chat Structure Creation
For 1:1 conversations between User A and User B:
- The administrator creates a group chat containing both users and themselves
- Messages are migrated into this chat structure
- After migration completes, the administrator account is automatically removed from the chat
- Users A and B can continue their conversation uninterrupted
Critical Considerations
Mapping Accuracy is Critical
User-to-user mappings must be completely accurate to prevent duplication. When migrating User A's messages:
- Conversations with User B become visible even if User B hasn't migrated yet
- When User B later migrates, duplicate detection automatically skips already-migrated messages
Message Injection Range Issues
Warning: Expanding the "Channel Messages Injection" date range setting after initial migration creates chronological ordering problems. Newly injected older messages appear after previously migrated ones, resulting in out-of-order message display.
Non-Recoverable Deletions
Deleted messages will not be re-migrated even after user recreation or migration restart. The system recognizes the prior migration status and skips these items.
Known Limitations
Chat Topic Display
One-to-one and group chats may have incomplete topic displays for some participants:
- User A sees the correct chat topic with all participant names
- Other participants may see incomplete topic displays (without User A's name)
- Solution: Users can manually edit the chat topic to include all names