How to Migrate from Kanboard to FrankBoard
How to Migrate from Kanboard to FrankBoard
Transition your existing project data to FrankBoard to gain a modernized interface while maintaining your current workflow. This process ensures a seamless upgrade without data loss.
What You'll Need
- Existing Kanboard installation
- Docker and Docker Compose installed on your host
- PostgreSQL database instance
- Administrative access to both environments
Steps
Step 1: Backup Kanboard Data
Create a full backup of your current Kanboard database and the 'data' directory. This ensures you have a recovery point before initiating the migration process.
Step 2: Prepare the FrankBoard Environment
Configure your docker-compose.yml file to define the FrankBoard image and link it to a PostgreSQL container. Ensure your environment variables for database credentials match your intended setup.
Step 3: Deploy FrankBoard via Docker
Run 'docker-compose up -d' to launch the FrankBoard containers. Verify that the web interface is accessible via your browser before attempting to import data.
Step 4: Export Kanboard Database
Use a database dump tool (such as pg_dump for PostgreSQL or mysqldump for MySQL) to export your Kanboard tables. Save this as a SQL file for the import phase.
Step 5: Import Data to FrankBoard
Upload your SQL dump into the FrankBoard PostgreSQL instance. Since FrankBoard is built on Kanboard, the schema is compatible, allowing for a direct data transfer.
Step 6: Sync Configuration Files
Move your custom configuration and uploaded attachments from the Kanboard 'data' folder to the FrankBoard volume. This preserves your project images and file attachments.
Step 7: Verify User Permissions
Log in to the new dashboard and verify that user roles, board permissions, and task assignments have transitioned correctly. Check that all swimlanes and columns are intact.
Step 8: Clear Cache and Test
Clear your browser cache and perform a test task movement to ensure the UI is interacting correctly with the migrated database. Confirm that all project links are functioning.
Expert Tips
- Perform the migration during low-traffic hours to avoid data collisions.
- Check for plugin compatibility, as some legacy Kanboard plugins may not be supported in the polished FrankBoard UI.
- Use a dedicated Docker network to ensure secure communication between the app and the database.