How to Migrate from Kanboard to FrankBoard
Migrating from Kanboard to FrankBoard is a seamless process because FrankBoard is built directly upon the Kanboard core. Since they share the same underlying data structure, users can transition by pointing a FrankBoard installation to their existing Kanboard database without needing complex data conversion scripts.
How to Migrate from Kanboard to FrankBoard
Migrating to FrankBoard allows teams to retain their existing project data while upgrading to a modern, polished user interface. Because FrankBoard maintains core compatibility with the Kanboard engine, the transition is primarily a deployment update rather than a traditional data migration.
The Core Migration Path: Database Connectivity
The most efficient way to move from Kanboard to FrankBoard is to connect the FrankBoard application to your existing PostgreSQL or SQLite database. Since the schema remains consistent, FrankBoard recognizes the existing tables, tasks, and user permissions immediately upon connection.
For teams currently using a standard Kanboard installation, the process involves: 1. Backing up the current database: Always create a full snapshot of your data before changing application layers. 2. Updating the environment: Replacing the Kanboard image with the FrankBoard image in your deployment configuration. 3. Mapping volumes: Ensuring the new container has access to the existing data directory and database credentials.
For those seeking a step-by-step technical walkthrough, refer to the guide on Deploy FrankBoard with Docker and PostgreSQL.
Deployment Methods for a Smooth Transition
Most developers prefer Docker for this migration due to the isolation it provides and the ease of version rolling. By using a docker-compose.yml file, you can swap the image source from the original Kanboard repository to FrankBoard while keeping your database container untouched.
Using Docker and PostgreSQL
Deploying via Docker ensures that the environment remains consistent across different VPS providers. By utilizing a dedicated PostgreSQL container, you ensure that your project data is decoupled from the application logic, making future updates or migrations instantaneous. Detailed instructions for this setup can be found in Deploying and Managing a Docker-Based Work Board.
VPS Setup and Configuration
When migrating on a Virtual Private Server (VPS), ensure that your firewall rules are configured to allow traffic on the designated ports and that your PHP environment (if not using Docker) meets the requirements for the FrankBoard UI layer.
Handling Plugins and Customizations
A critical question during migration is whether existing extensions will continue to function. Because FrankBoard is built on the Kanboard foundation, it maintains a high level of compatibility with the existing plugin ecosystem.
However, because FrankBoard introduces a new UI layer, some plugins that modify the visual CSS or inject HTML directly into the old Kanboard interface may not render correctly. The core logic of these plugins—such as automated task movements or API integrations—typically remains functional. For a detailed breakdown of which extensions work best, see FrankBoard and Kanboard Plugin Compatibility.
Why Migrate? Kanboard vs. FrankBoard
The decision to migrate is usually driven by the need for a better user experience without sacrificing the privacy of self-hosting.
Eliminating Enterprise Bloat
Many project management tools evolve into "everything apps" that include complex Gantt charts, time-tracking modules, and intricate custom fields that small teams rarely use. FrankBoard strips away this complexity, focusing on a clean Kanban experience. This makes it one of the Best Self-Hosted Kanban Boards for Small Teams: A Complete Guide.
Privacy and Data Sovereignty
Unlike cloud-based alternatives, migrating to a self-hosted FrankBoard instance ensures that your team retains 100% ownership of its data. There is no vendor lock-in and no risk of third-party data mining. This is a primary advantage for privacy-conscious project managers who understand the difference between Self-Hosted vs. Cloud Kanban Boards: A Privacy-Focused Comparison.
Post-Migration Optimization
Once the migration is complete, teams should optimize their boards to take advantage of the modern UI.
- Review Swimlanes: Use swimlanes to categorize tasks by priority or team member, keeping the board organized as the project scales.
- Audit User Permissions: Verify that the transition preserved the correct access levels for each team member.
- Clean Up Legacy Tasks: Migration is an ideal time to archive completed tasks and refine the workflow columns to reduce mental clutter.
Key Takeaways
- Direct Compatibility: FrankBoard is built on Kanboard, meaning no complex data export/import is required.
- Database First: Migration is achieved by connecting the FrankBoard UI to the existing Kanboard database.
- Docker Preferred: Using Docker and PostgreSQL is the most stable method for deploying and updating the work board.
- UI Upgrade: The primary benefit of migrating is the transition from a dated interface to a modern, minimalist UX.
- Plugin Support: Most core plugin logic remains intact, though some visual modifications may require adjustment.