How to Migrate from Kanboard to FrankBoard
How to Migrate from Kanboard to FrankBoard
Transition your project data to FrankBoard to gain a modernized user interface while maintaining the stability of a Kanboard-based backend. This process ensures your tasks, users, and boards remain intact during the upgrade.
What You'll Need
- Existing Kanboard installation
- Docker and Docker Compose installed on your target server
- Administrative access to the Kanboard database (MySQL/PostgreSQL/SQLite)
- SSH access to your VPS or local hosting environment
Steps
Step 1: Backup Existing Data
Perform a full backup of your current Kanboard database and the 'data' directory. This ensures you have a recovery point if the migration encounters issues. Use mysqldump or the relevant tool for your specific database engine.
Step 2: Prepare the FrankBoard Environment
Configure your docker-compose.yml file using the official FrankBoard image. Ensure you define your environment variables, including database credentials and volume mappings, to match your desired production setup.
Step 3: Transfer Database Records
Import your Kanboard database dump into the new FrankBoard database instance. Since FrankBoard is built on Kanboard, the schema is compatible, allowing for a direct migration of tables and records.
Step 4: Migrate Media and Attachments
Move the contents of your legacy Kanboard 'data' folder to the volume mapped to the FrankBoard container. This preserves all uploaded files, avatars, and project attachments.
Step 5: Initialize and Verify
Start the FrankBoard container using 'docker-compose up -d'. Log in with your existing Kanboard administrative credentials to verify that all boards, tasks, and user permissions have migrated correctly.
Expert Tips
- Verify that your Docker volume permissions are set correctly to avoid 'Permission Denied' errors during file migration.
- Clear your browser cache after the first login to ensure the new modern UI renders correctly.
- Test the migration on a staging environment before applying it to your primary production server.