Move to Slack

The largest gap is permission scope. The process page says Teams or Google Chat is connected with read-only API access. Yet the Google admin setup publishes scopes for message and space creation/deletion, writable admin directory access, `cloud-platform`, BigQuery, full-control Cloud Storage, Datastore, Logging, Monitoring, and Trace, with duplicated BigQuery entries. The MS Teams page likewise lists application-wide organizational reads alongside delegated app-registration writes, channel deletion, message and chat writes, file writes, SharePoint full control, and group/member writes. It does not identify which scopes the current product actually requests, which belong to source versus destination, why each is needed by migration phase, what can be removed, the least-privilege bundles, or token storage, rotation, revocation, and admin audit. 'Read-only' therefore is not supported by the current public setup material. The data boundary is also incomplete. Home says no local server storage and zero retention; the process says no data retained beyond the migration window; the introduction only says no external-server storage after migration. The second maker graphic says data is scrubbed after transfer, while the third says no data leaves customer systems. None defines the migration window, transient location, whether Salesforce counts as vendor infrastructure, how attachments travel, how long retries, logs, backups, validation reports, and tokens persist, or what deletion evidence customers receive. The privacy policy defines the Service as the Website and generically covers contact data, addresses, Usage Data, cookies, marketing, international processing, and retention as necessary. It does not cover source messages, DMs, files, directories, OAuth secrets, mappings, migration logs, failures, processors, regions, encryption, incident notice, a DPA, or concrete deletion periods. The terms likewise primarily govern website access, without migration scope, SLA, data processing, security schedule, backup/recovery, refund, or acceptance terms. Published marketing metrics lack methods: the hero combines 2,800+ workspaces with 99.98% data-match accuracy, while the footer says 1M+ messages, 500+ teams, and 99.9% success. Workspace/team and data-match/success may be distinct, but no sample, period, denominator, or independent evidence is supplied. Compliance language also drifts: Home says SOC 2 and HIPAA-aligned, the introduction says GDPR, SOC2, and HIPAA aligned, and the maker graphic says SOC 2, misspells HIPAA as HIPPA, and says GDPR compliant. No report, audit scope, issuer, BAA, DPA, region, or control mapping was found. Uneed labels pricing Free, while the official site only offers a sales call and publishes no price, trial, license, or Salesforce/Slack plan prerequisites; free use is therefore unverified. Salesforce-native architecture, real-time sync, zero downtime, complete migration, 99.98% matching, 500+ teams, and 2,800+ workspaces are team statements. We found no customer case, reproducible test, public app manifest, or contract material to independently establish them.