FrankBoard Compatibility Matrix: Supported Kanboard Plugins and Features
FrankBoard Compatibility Matrix: Supported Kanboard Plugins and Features
FrankBoard preserves most core Kanboard functionality while modernizing the interface, though plugin compatibility varies based on whether extensions rely on the legacy PHP frontend or hook into backend APIs. Small teams migrating from Kanboard can expect full data fidelity for tasks, projects, and swimlanes, with partial support for visual plugins that modify the classic theme.
Core Kanboard Features: Full Compatibility
The following foundational capabilities work identically in FrankBoard, as they operate through Kanboard's database and API layers rather than the legacy presentation layer.
| Feature | Status | Notes |
|---|---|---|
| Kanban boards with columns | Yes | Native to both systems; drag-and-drop persists via same backend |
| Swimlanes | Yes | Fully supported; visual rendering updated in FrankBoard UI |
| Task creation and editing | Yes | All fields, subtasks, and metadata preserved |
| Automatic actions (webhooks) | Yes | Trigger logic unchanged; configured through same rule engine |
| Project roles and permissions | Yes | ACL system inherited directly |
| CSV import/export | Yes | File format identical; no migration friction |
| API (JSON-RPC/REST) | Yes | All endpoints accessible; FrankBoard adds no breaking changes |
| PostgreSQL/MySQL/SQLite | Yes | Database schemas remain compatible |
| LDAP/SSO authentication | Yes | Backend integrations untouched |
| Email notifications | Yes | Same SMTP and digest configuration |
Plugin Compatibility: The Deciding Factor
FrankBoard's redesigned React frontend filters which Kanboard plugins function correctly. Plugins fall into three categories: backend-only extensions (generally compatible), theme-dependent visual plugins (typically incompatible), and mixed plugins requiring evaluation.
| Plugin Category | Representative Examples | Status | Reasoning |
|---|---|---|---|
| Backend integrations | GitHub/GitLab webhooks, Slack notifications | Yes | Operate via API hooks and database; UI agnostic |
| Authentication extensions | OAuth2 providers, SAML, 2FA backends | Yes | Execute before FrankBoard's presentation layer loads |
| Task automation | Custom automatic actions, cron-based schedulers | Yes | Server-side PHP; no frontend dependency |
| Theme overrides | Custom CSS injectors, color scheme plugins | No | Target Kanboard's PHP template system, which FrankBoard replaces |
| Dashboard widgets | Gantt charts, calendar views, analytics panels | Partial | Data accessible via API; requires FrankBoard-native rendering or iframe embedding |
| Board visualizations | Card styling plugins, WIP limit indicators | Partial | Backend rules enforced; visual cues may need FrankBoard CSS equivalents |
| Third-party integrations | Mattermost, Discord, Jira bridges | Yes | API-to-API communication; unaffected by UI layer |
Specific Plugin Evaluations
Fully Supported: Webhook and Notification Plugins
Plugins like Slack, Discord, Rocket.Chat, and Matrix integrations function without modification. These extensions listen for Kanboard events and push to external services—FrankBoard generates identical event payloads. Teams using these for CI/CD pipelines or incident response need not reconfigure anything during migration.
Partially Supported: Gantt and Calendar Views
Plugins such as Gantt and Calendar compute task scheduling data server-side, which FrankBoard can access. However, their rendered HTML assumes Kanboard's CSS framework. FrankBoard offers native timeline and calendar views that consume the same underlying data, serving as functional replacements rather than direct plugin continuations.
Not Supported: Theme and Layout Modifiers
Plugins including ThemePlus, Customizer, and Bigboard directly manipulate Kanboard's PHP templates and CSS variables. FrankBoard's component-based architecture renders these inoperative. Teams relying on heavy visual customization should evaluate FrankBoard's built-in theming variables or plan for custom React component development.
Database and Migration Considerations
FrankBoard maintains schema parity with Kanboard, enabling zero-downtime migrations for standard installations. The critical compatibility checkpoint is plugin-generated database tables:
| Scenario | Migration Path |
|---|---|
| Core tables only | Direct PostgreSQL/MySQL dump and restore |
| Plugin tables with backend data | Preserved; functionality depends on plugin category above |
| Plugin tables with frontend config | Data retained but may require manual mapping to FrankBoard equivalents |
Docker deployments using official Kanboard images transition cleanly when volumes and database connections remain consistent. Environment variables for database DSNs, SMTP, and LDAP transfer without syntax changes.
API-First Extension Strategy
Developers building new integrations for FrankBoard should target Kanboard's stable REST/JSON-RPC APIs rather than frontend hooks. This approach guarantees forward compatibility regardless of UI evolution. FrankBoard exposes identical endpoints with identical authentication requirements, making it a drop-in replacement for headless Kanboard deployments.
Existing plugins with substantial backend logic can often be preserved by adding a thin API adapter layer, separating business rules from presentation concerns that FrankBoard handles natively.
Key Takeaways
- FrankBoard achieves full compatibility with Kanboard's data layer and API ecosystem, ensuring no task, project, or user information is lost during migration
- Backend plugins (webhooks, notifications, authentication, automation) require zero changes and operate identically
- Visual plugins dependent on Kanboard's PHP theme system need replacement with FrankBoard-native alternatives or custom development
- Mixed plugins like Gantt charts retain their data models but require UI reimplementation; FrankBoard provides comparable native views
- Migration risk concentrates in heavily customized Kanboard instances with numerous theme plugins; audit these before committing to FrankBoard
- The safest migration path preserves existing Docker volumes and database connections, then validates plugin functionality incrementally