{"id":73156,"plugin_id":"plugin_asdk_app_6acb9d0a0498819182237d377bf71884","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-31T01:18:53.773Z","digest":"b8f6b34d86954155b229c9fb3627bb67be66cca88dbe7208c644f85497e0d402","against":null,"payload":{"description":"Plan and guide a move from Slack to Ando using native Slack sync, verified channel and identity mappings, a pilot, and cutover checks. Use for Slack migration or history-backfill requests.","included_files":[],"name":"ando-migrate-slack","skill_md_contents":"---\nname: ando-migrate-slack\ndescription: Plan and guide a move from Slack to Ando using native Slack sync, verified channel and identity mappings, a pilot, and cutover checks. Use for Slack migration or history-backfill requests.\n---\n\n# Migrate from Slack\n\nRead the [shared migration workflow](../../references/migration-workflow.md).\nUse the current [Slack import and sync guide](https://docs.ando.so/docs/importing-from-slack)\nto verify setup, supported channels, history coverage, and message support.\n\n## Choose the supported path\n\nAndo's documented native route is **Settings → Slack sync**: connect the\nauthorized Slack workspace, select accessible public or private channels\n(including Slack Connect channels), and map them to new or existing Ando\nchannels. Private channels require the private-channel consent scopes and the\nviewing member's own Slack access; review the destination membership before\nenabling private sync. DMs are not selectable. The documented backfill is up to\n180 days and runs in the background. Verify current behavior and access before\nquoting these limits; do not promise a whole-workspace or unlimited-history import.\n\nIf the user needs history beyond native backfill or unsupported DMs, assess an authorized\nexport and a supported history-import route separately. Do not imply Slack\nadmin rights, export availability, or an existing ZIP importer without evidence.\nIf no supported executor is available, produce the mapping and explain the\nspecific manual/operator step instead of inventing an MCP migration tool.\n\n## Pilot and read back\n\nStart with a selected public channel when authorized. Review its target\nmembership before mapping a Slack Connect channel; shared-channel history\nmust not become visible to unintended people. Check identity matches, source\nlinks, representative history, and channel-level sync/backfill progress in\nSettings. Verify new-message delivery separately from historical coverage.\n\nOutbound posting is workspace-dependent. Check availability and the sending\nmember's Slack connection before testing it. The documented outbound route\nsupports new human text messages, not all edits, deletes, files, reactions, or\nagent-authored messages. Do not infer two-way fidelity from inbound sync.\n\nKeep existing mappings and checkpoints for resume. Disconnecting stops sync\nbut retains synced messages, members, and paused mappings; it is not an undo.\nGuide the requested cutover only after coverage and gaps are understood.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}