monday.com Migration
Teams running monday.com as a CRM can migrate boards, items, and timeline history into Strkr. Board columns map to Strkr fields; status columns map to pipeline stages. Dry-run preview before commit.
Everything monday.com Migration does inside Strkr.
- Board-to-pipeline migration
- Column-to-field mapping
- Status-column to stage mapping
- Dry-run preview
Native code, not a shim.
OAuth where available
monday.com Migration will ship with a native OAuth flow when it lands. No pasted credentials for admins to rotate manually.
KMS-encrypted tokens
Access and refresh tokens are envelope-encrypted at rest using a dedicated customer-managed KMS key. Decryption only happens in Lambda memory during an active API call; plaintext tokens never land in a log.
Shared by the workspace
A workspace admin connects monday.com Migration once; every teammate uses the shared connection without re-authenticating.
Disconnect at any time
Admins or users can disconnect monday.com Migration from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.
monday.com Migration is on the roadmap.
We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If monday.com Migration is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.