How to Migrate from Kanboard to FrankBoard Without Data Loss
How to Migrate from Kanboard to FrankBoard Without Data Loss
Transition your existing project workflows to FrankBoard while preserving all task history and board configurations. This process ensures a seamless move from a standard Kanboard installation to the polished FrankBoard UI.
What You'll Need
- Active Kanboard installation with administrative access
- Docker and Docker Compose installed on the target server
- PostgreSQL instance configured for FrankBoard
- SSH access to the hosting VPS
Steps
Step 1: Backup Existing Data
Create a full snapshot of your current Kanboard database and the 'data' directory. This ensures you have a recovery point if the migration requires a restart or if configuration errors occur.
Step 2: Prepare the FrankBoard Environment
Deploy FrankBoard using the official Docker image and a PostgreSQL database. Ensure the container is running and reachable via your browser to verify the initial installation is stable.
Step 3: Export Kanboard Database
Use the mysqldump utility or your database management tool to export the Kanboard schema and data into a SQL file. Ensure the export includes all project, task, and user tables to prevent data gaps.
Step 4: Map Data Schemas
Review the database mapping between the legacy Kanboard structure and the FrankBoard requirements. Since FrankBoard is built on Kanboard, the underlying logic is compatible, but verify that custom fields are mapped correctly.
Step 5: Import Data to PostgreSQL
Import the exported SQL data into the FrankBoard PostgreSQL instance. Use the psql command-line tool or a GUI client to execute the script and populate the new database.
Step 6: Sync Media and Attachments
Transfer the 'data' folder from the old Kanboard installation to the FrankBoard Docker volume. This preserves all uploaded files, task attachments, and user avatars.
Step 7: Verify Permissions
Adjust the ownership and permissions of the migrated data folder using chown and chmod. This prevents 'Permission Denied' errors when FrankBoard attempts to read or write attachments.
Step 8: Final Validation
Log in to the FrankBoard interface and verify that all projects, swimlanes, and task histories are intact. Test a few task movements to ensure the database is writing correctly.
Expert Tips
- Perform a dry run on a staging environment before updating your production server.
- Check for plugin compatibility, as some legacy Kanboard plugins may not be supported in the polished FrankBoard UI.
- Keep your old Kanboard instance offline but preserved for 30 days after migration for auditing purposes.