Migrating to S-unno (formerly MediaRing Talk): A Quick Guide

Migrating to S-unno (formerly MediaRing Talk): A Quick Guide

1. Overview

S-unno is the rebranded platform formerly known as MediaRing Talk. This guide assumes you’re moving from MediaRing Talk or another communication platform and need a concise, practical migration plan.

2. Pre-migration checklist

1. Inventory: List accounts, user roles, channels, integrations, bots, and archived messages to migrate.
2. Data export: Export user data, message history, files, and settings from the source platform in available formats (CSV, JSON, ZIP).
3. Permissions map: Record current permission levels and group memberships to replicate in S-unno.
4. Integrations list: Note connected apps (calendar, CRM, storage, SSO, webhook endpoints) and required API keys.
5. Compliance & retention: Confirm legal, retention, and backup requirements for message and file retention.
6. Stakeholders: Identify admins, IT, and power users who’ll run or validate the migration.

3. Migration approach (recommended)

1. Pilot: Select a small team (5–15 users) and one or two channels to test a full migration.
2. Map data structure: Translate source channels/groups, user IDs, and metadata to S-unno equivalents.
3. Import users first: Provision accounts (or configure SCIM/SSO) and verify authentication flows.
4. Move messages & files: Use exported archives or S-unno import APIs; preserve timestamps and authors where possible.
5. Recreate integrations: Reconnect apps and reconfigure webhooks, calendars, and storage links.
6. Permissions & settings: Apply mapped roles and channel-level permissions.
7. Validation: Have pilot users verify message integrity, search, file access, and integrations.
8. Full migration: Schedule and run bulk migration during low-usage hours; monitor for errors.
9. Cutover: Update DNS/links, disable old platform access, and announce the change.
10. Post-migration support: Provide help docs, training sessions, and a short rollback window if critical issues arise.

4. Technical tips

• Timestamps & authors: If direct preservation isn’t possible, import as system-posted messages with original metadata included in the message body.
• Rate limits: Respect S-unno API rate limits; implement exponential backoff for retries.
• Large files: Migrate large attachments via cloud storage links and re-link rather than re-upload where possible.
• Search indexing: Trigger or wait for S-unno’s indexing process before declaring migration complete.
• SSO/SCIM: Test provisioning, deprovisioning, and group sync with a single test account first.
• Automation: Script repetitive tasks (user creation, permission assignment) to reduce human error.

5. Communication plan

• Pre-migration announcement: Share timeline, expected downtime, and training resources 1–2 weeks prior.
• Day-of updates: Provide status updates via email/temporary chat channel.
• Post-migration: Send checklist for users (log out/in, update bookmarks, reconnect integrations) and a guide to changes in UI/behavior.

6. Rollback considerations

• Keep the old platform in read-only mode for a defined window (e.g., 7–14 days).
• Maintain exported backups of messages and files until final sign-off.
• Define clear criteria that would trigger rollback (data loss, authentication failures, critical integration breakage).

7. Post-migration checklist

• Confirm all users can authenticate and access expected channels.
• Verify message history completeness and file accessibility.
• Test critical integrations and automation.
• Collect user feedback and address top issues within 72 hours.
• Archive migration logs and document lessons learned.