Move with a plan
Switching from twigpine
What leaving twigpine involves, worked out from what its own pages publish: how the data comes out, what a replacement has to match, what the overlap costs. Where twigpine does not publish something, this page says so instead of guessing.
twigpine's pages last read Nov 9, 2026.
The move, step by step
- 1
Find out how your data comes out
No export format is recorded for twigpine. Before choosing a replacement, ask its support what can be exported, in which format, and whether history and attachments are included.
Not published by twigpine
- 2
List what the replacement must match
Recorded for twigpine: Every push is signed; Identity on the network is an Ed25519 keypair, written as a did:key; OpenGateway provides one endpoint and supports 21 models. Mark the ones your team uses and check each against the replacement's plan, not its marketing page.
- 3
Budget for the overlap
Both subscriptions run while you move. On Monthly plan, twigpine for 10 people is about $10 a month at published prices, so each month of overlap costs that on top of the replacement.
- 4
Move a sample, then everyone
Import a small, real slice into the replacement and test permissions, automations and links before moving the team. Cancel only after the data is verified, and read the retention terms: how long your data stays available after cancelling.
No alternative has been checked against twigpine yet. Browse products in the same category