Menu

Individual skill

cometchat-migrate-from-sendbird

Migrate an app from Sendbird to CometChat end-to-end in ONE prompt, on any platform in this pack (React, Angular, React Native/Expo, iOS, Android, Flutter). Inventories every Sendbird usage (Chat SDK v3/v4, UIKit, Calls, Desk, push, server Platform API, webhooks), swaps each supported feature for its CometChat equivalent, REMOVES features CometChat has no equivalent for (code, UI, deps), writes a data-migration script for users/groups/history, uninstalls Sendbird, verifies the build, and ends with a report listing what was migrated, what was removed and what you still need to do. Triggers: 'migrate my app from Sendbird to CometChat', 'migrate my app to CometChat' (Sendbird detected), 'replace Sendbird with CometChat', 'switch from Sendbird', 'move off Sendbird', 'sendbird to cometchat', 'port my Sendbird chat to CometChat', 'migrate only my data from Sendbird', 'import my Sendbird data into CometChat'.

plugins/cometchat/cometchat-skills/skills/cometchat-migrate-from-sendbird/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

> **Ground truth:** the SENDBIRD side (what to look for) is baked in `references/inventory.md` + `references/feature-map.md` — confirm each hit by reading the user's code. The COMETCHAT side is never from memory: symbols come from the target family's skills + catalog, feature existence from that family's `features.json`, signatures from the docs via the family's `-core/references/docs-map.md` (Docs MCP first — `RULES.md` → Fetch discipline). REST pages live under `DOCS_BASE` = `https://www.cometchat.com/docs`.

## Companion skills (read first)
- `cometchat-<family>-core` — the init → login → render the migrated app lands on. `<family>` is resolved in step 1; this skill ASSUMES that core and never restates its code.
- `cometchat-<family>-components` / `-features` / `-calls` / `-push` / `-customization` — pulled in only for the Sendbird features the inventory finds.

## Use this skill when
The user asks to move an app off Sendbird: "migrate my app from Sendbird to CometChat", "replace Sendbird", "switch to CometChat", or "migrate my app to CometChat" when `npx @cometchat/skills detect --json` reports `migrate_from` with vendor `sendbird`. Stream/GetStream apps → `cometchat-migrate-from-getstream`. An app with BOTH vendors: run both skills, one after the other, into one report.
**Data only** ("migrate only my data", "import my Sendbird users and messages", "don't change my code", or the app already runs on CometChat) → follow `references/data-only.md` INSTEAD of the workflow below: it writes and runs the data script and changes nothing else.

## The single-prompt contract (read before step 1)
The migration request IS the approval (`RULES.md` → Competitor migration). Run every step below to the end in this one turn:
- **Do not stop to ask.** No onboarding plan/approve gate, no clarification questions. Where a companion skill would ask, take the default written here, and record it under *Defaults taken* in the report.
- **Safety net instead of questions:** in a git repo, first `git switch -c cometchat-migration` (carries any uncommitted work along; mention that in the report). Never commit, push, or rewrite history. No git → proceed and say so in the report.