Migrating from Kanboard to FrankBoard: A Complete Guide
Migrating from Kanboard to FrankBoard: A Complete Guide
Transitioning your project management to FrankBoard is straightforward because it is built upon the Kanboard foundation. This guide details how to move your data while upgrading to a modern, polished user interface.
How do I migrate my existing Kanboard data to FrankBoard?
Since FrankBoard is built on Kanboard, migration is primarily a matter of pointing the FrankBoard installation to your existing Kanboard database. If you are using Docker, you can simply map your current database volume to the FrankBoard container to preserve all tasks, boards, and user accounts.
Is the migration from Kanboard to FrankBoard reversible?
Yes, because FrankBoard maintains compatibility with the underlying Kanboard data structure. You can switch back to a standard Kanboard installation by reconnecting your database to a vanilla Kanboard image without losing your core project data.
Will I lose my project history or task comments during the transition?
No, all historical data, including task descriptions, comments, and activity logs, is preserved. FrankBoard acts as a modern interface layer over the existing data schema, ensuring your project audit trails remain intact.
How do I deploy FrankBoard using Docker and PostgreSQL for the first time?
The most efficient method is using a docker-compose file that defines two services: the FrankBoard application image and a PostgreSQL database image. Ensure you configure the environment variables for database credentials and persistent volume mounts to prevent data loss during container restarts.
Are Kanboard plugins compatible with FrankBoard?
While FrankBoard is built on Kanboard, its primary goal is to provide a streamlined, polished UI without the bloat of complex plugins. Some core functionalities may differ, and users should verify specific plugin compatibility through the official documentation before expecting full integration.
What are the primary UI differences after migrating to FrankBoard?
Users will notice a significant shift from the legacy Kanboard aesthetic to a minimalist, modern interface. The transition focuses on reducing visual clutter and improving the user experience for small teams without changing the fundamental Kanban logic.
Can I migrate from a cloud-hosted Kanboard instance to a self-hosted FrankBoard setup?
Yes, provided you have a full database export (SQL dump) from your cloud provider. You can import this dump into your local PostgreSQL or SQLite database before launching the FrankBoard Docker container.
Does FrankBoard support the same user permissions as Kanboard?
Yes, FrankBoard inherits the robust permission system of Kanboard. Your existing user roles, group assignments, and board-level access controls will remain active after the migration.
How do I handle the migration if I am using a VPS?
On a VPS, the recommended approach is to install Docker and Docker Compose. Once the environment is ready, deploy the FrankBoard image and link it to your existing database volume or a remote PostgreSQL instance.
Will migrating to FrankBoard affect my API integrations?
Because FrankBoard maintains the Kanboard core, most standard API endpoints remain functional. However, it is recommended to test any custom scripts or third-party integrations immediately following the migration to ensure seamless connectivity.
Is a manual data export required to move to FrankBoard?
A manual export is only necessary if you are changing database engines (e.g., moving from SQLite to PostgreSQL). If you are staying on the same database type, simply mounting the data volume to the new FrankBoard container is sufficient.
See also
- The Best Self-Hosted Kanban Board for Small Teams: A Complete Guide
- Deploy FrankBoard with Docker and PostgreSQL
- Self-Hosted vs. Cloud Kanban Boards: A Privacy-Focused Comparison
- FrankBoard and Kanboard Plugin Compatibility