How to Migrate from Kanboard to FrankBoard Without Data Loss
How to Migrate from Kanboard to FrankBoard Without Data Loss
This guide provides a streamlined process for transitioning your existing Kanboard data to FrankBoard, ensuring a seamless move to a modern interface while preserving your project history.
What You'll Need
- Existing Kanboard installation
- Docker and Docker Compose installed
- Administrative access to the server/VPS
- A recent backup of the Kanboard database
Steps
Step 1: Backup Current Data
Create a full snapshot of your Kanboard database and any associated file uploads. This ensures you have a recovery point if the migration process is interrupted or requires a restart.
Step 2: Prepare the FrankBoard Environment
Configure your docker-compose.yml file to include the FrankBoard image and a PostgreSQL database. Ensure the network settings allow the application to communicate with the database container.
Step 3: Export Kanboard Database
Use the mysqldump utility or your database management tool to export the Kanboard data into a SQL format. Verify that the export includes all project boards, task lists, and user accounts.
Step 4: Initialize FrankBoard Containers
Deploy the FrankBoard containers using 'docker-compose up -d'. Allow the system to complete its initial boot sequence and create the base directory structures on your host machine.
Step 5: Import Data to PostgreSQL
Import your exported SQL data into the FrankBoard PostgreSQL instance. Use the docker exec command to run the import process directly within the database container to avoid permission issues.
Step 6: Verify Schema Compatibility
Check that the imported tables align with the FrankBoard requirements. Since FrankBoard is built on Kanboard, the core data structures are compatible, but a quick check for missing indices is recommended.
Step 7: Configure Environment Variables
Update your .env file with the correct database credentials and application secrets. Restart the containers to apply these changes and establish a secure connection to the migrated data.
Step 8: Perform a Final Data Audit
Log into the FrankBoard interface and verify that all boards, swimlanes, and task assignments are present. Test a few task movements to ensure the database write permissions are functioning correctly.
Expert Tips
- Run the migration in a staging environment first to avoid downtime on your production board.
- Ensure your VPS has sufficient RAM to handle the simultaneous operation of both containers during the transition.
- Check that file upload paths in your old configuration match the volume mounts in your new Docker setup.