How to Migrate from Kanboard to a Modern UI Without Losing Data
How to Migrate from Kanboard to a Modern UI Without Losing Data
Upgrade your project management experience by transitioning from a standard Kanboard installation to FrankBoard. This process preserves your existing data while providing a polished, developer-centric interface.
What You'll Need
- Existing Kanboard installation
- Docker and Docker Compose installed on your VPS or server
- Administrative access to the host machine
- A recent backup of your Kanboard database
Steps
Step 1: Backup Existing Data
Create a full snapshot of your current Kanboard database and configuration files. This ensures you have a recovery point before introducing any new software layers or modifying your environment.
Step 2: Prepare the Docker Environment
Install Docker and Docker Compose on your target server. Ensure the necessary ports are open and that you have a dedicated directory for the FrankBoard deployment to keep your file structure organized.
Step 3: Configure the Docker Compose File
Set up the FrankBoard docker-compose.yml file. Define your environment variables, including database credentials and port mappings, to ensure the new UI can communicate with your data store.
Step 4: Connect to the Kanboard Database
Point the FrankBoard instance toward your existing Kanboard database. Because FrankBoard is built upon the Kanboard core, it recognizes the underlying data schema, eliminating the need for complex ETL processes.
Step 5: Deploy the FrankBoard Container
Run the deployment command to pull the latest image and start the service. Monitor the logs to confirm that the application has successfully initialized and connected to the database.
Step 6: Verify Data Integrity
Log in to the new interface using your existing Kanboard credentials. Navigate through your boards, tasks, and user assignments to confirm that all historical data has migrated correctly.
Step 7: Optimize VPS Settings
Adjust your reverse proxy or firewall settings to route traffic to the new FrankBoard port. This ensures a professional URL structure and secure HTTPS access for your team.
Expert Tips
- Perform a dry run on a staging server to verify compatibility before updating your production environment.
- Use a dedicated volume for your Docker containers to ensure persistent storage and easier future updates.
- Keep your original Kanboard installation dormant for a few days to ensure no data gaps exist before full decommissioning.