How to migrate from Canny to Fider
Technical infrastructure migrations vary a lot depending on the tool — these are the general steps that apply to most cases.
- 1
Export your configuration and data from Canny
Check Canny's documentation for exporting projects, configuration and integrations — the exact format depends on the service, but almost all offer some export path for paid accounts.
- 2
Prepare the Fider environment
Deploy Fider in a staging environment first (not production) and replicate the base configuration before moving any real data.
- 3
Migrate in pieces and validate each one
Move one project or integration at a time instead of all at once, checking that each piece works in Fider before moving on to the next.
- 4
Update integrations that depended on Canny
Any external service (CI/CD, webhooks, SDKs) that pointed at Canny needs to be reconfigured to point at your new Fider instance.
Before cancelling Canny
Before cancelling Canny, confirm no production service still depends on it by checking recent access logs.
Ready to deploy Fider?
Full profile with license, tech stack and ready-to-copy docker-compose.
View Fider's profileThese steps are a general guideline — the exact export menu can vary depending on Canny's plan and version.