How to Migrate from Kanboard to FrankBoard Without Data Loss
How to Migrate from Kanboard to FrankBoard Without Data Loss
Transition your existing project data to FrankBoard to upgrade your user interface while maintaining full control over your database. This process ensures all historical tasks and board configurations remain intact during the shift.
What You'll Need
- Existing Kanboard installation
- Docker and Docker Compose installed
- PostgreSQL database access
- Administrative access to the VPS or host server
Steps
Step 1: Backup Existing Data
Create a full snapshot of your current Kanboard database and configuration files. Use pg_dump for PostgreSQL or the native backup tool of your current database engine to ensure you have a recovery point before modifying any data.
Step 2: Prepare the Environment
Ensure your server meets the minimum requirements for FrankBoard. Stop the active Kanboard container to prevent write operations during the migration process, avoiding potential data corruption.
Step 3: Configure Docker Compose
Update your docker-compose.yml file to point to the FrankBoard image. Ensure the volume mappings for your database remain consistent so the new interface can locate the existing data store.
Step 4: Connect the Database
Input your existing database credentials into the FrankBoard environment variables. Verify that the database user has the necessary permissions to read and write to the existing Kanboard schema.
Step 5: Initialize FrankBoard
Deploy the FrankBoard container using the 'docker-compose up -d' command. The system will automatically detect the existing database structure and apply the modern UI layer over your current data.
Step 6: Verify Data Integrity
Log in with your previous Kanboard credentials and audit your boards, tasks, and user assignments. Confirm that all historical task descriptions and attachments have migrated correctly to the new interface.
Step 7: Optimize Performance
Clear your browser cache and restart the container to ensure all static assets are loading from the FrankBoard UI. Check the system logs for any migration warnings or deprecated plugin conflicts.
Expert Tips
- Run the migration in a staging environment first to test compatibility with custom plugins.
- Verify that your PostgreSQL version is compatible with the latest FrankBoard Docker image.
- Keep a copy of your original Kanboard config.php file for quick reference of custom settings.
- Use a dedicated volume for your database to simplify future updates and backups.