Migrate your Rukovoditel data
Self-hosted PHP project management and CRM builder with a free tier and no vendor lock-in, but no native bulk export API.
In its favor
Why people choose Rukovoditel
The signal that keeps Rukovoditel on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Free and open source with no per-seat or per-record licensing, making it attractive for budget-constrained small businesses and nonprofits that need a fully configurable CRM without a recurring cost.
Highly flexible Database Designer allows teams to model any vertical workflow by creating custom Entities, Fields, and Relationships without code.
Lightweight PHP/MySQL stack runs on any shared hosting or low-cost VPS, appealing to teams with limited IT infrastructure.
Active development and regular feature additions keep the platform competitive against paid alternatives for small teams.
Simple installation with no vendor dependency gives complete data sovereignty and avoids subscription lock-in.
No native bulk export or well-documented API makes data portability difficult as the team scales beyond a few hundred records.
Absence of modern collaboration features like real-time co-editing, Slack-style notifications, and mobile-native apps lags behind SaaS PM tools.
Limited third-party integrations compared to established platforms; most connectors must be built and maintained manually.
Self-hosting burden falls on the customer — updates, security patches, backups, and server maintenance require ongoing IT attention.
Performance degrades noticeably on larger datasets without proper indexing, affecting teams managing thousands of records.
Reasons to switch
Why people leave Rukovoditel
The recurring reasons buyers give for replacing Rukovoditel. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Rukovoditel fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Rukovoditel pricing overview
Rukovoditel is free open-source software for self-hosting, with no built-in licensing restrictions on users or records. The vendor offers a cloud-hosted managed option at an undisclosed per-user or per-month rate. Most customers use the free self-hosted version, which eliminates software cost but shifts infrastructure and maintenance expense to the customer's team.
Free (Self-hosted)
Tier 1 of 2
Free (open source)
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Rukovoditel's schedule — see our quote-based pricing →
What gets migrated
Rukovoditel object support
Object-by-object support for Rukovoditel migrations. Per-pair details surface during scoping.
Entities
Mapping requiredEntities are the core data objects in Rukovoditel — essentially user-defined database tables created via the Database Designer. Every installation has a different set of Entities, so we always introspect the actual entity list first and build a custom field map for each one.
Fields
Mapping requiredStandard and custom fields are created per-Entity with a wide variety of types (text, number, date, entity reference, related records, users, user groups, MySQL query). Field IDs are numeric and unique per application, not globally consistent. We capture the full field definition including type, required flag, and validation rules during schema review.
Nested Entities (one-to-many)
Mapping requiredNested Entities represent one-to-many parent-child relationships and are implemented as separate tables with a foreign key back to the parent. We resolve this relationship and map it to the destination's equivalent (e.g., sub-tasks, child records) preserving the hierarchy at import time.
Related Records (many-to-many)
Mapping requiredMany-to-many relationships use the Related Records field type, storing associations in a junction table. We extract the relationship table, map both sides of the association, and reconstruct it in the destination using that platform's native linking mechanism.
Users and User Groups
Mapping requiredRukovoditel Users and User Groups are separate objects tied to access control rules on Entities and Fields. We map user accounts to the destination's owner/assignee model and preserve group memberships as team or role assignments where supported.
Attachments
Mapping requiredFile attachments are stored on the server filesystem with references in the database. We export the binary files, preserve their record associations, and re-upload them to the target system's attachment storage. Inline images use the same path.
XML Export Templates
Mapping requiredRukovoditel's XML Export uses user-defined templates referencing fields by [field ID] notation. We parse the template logic to understand which fields are included and in what structure, then reconstruct equivalent field mappings for the destination import.
Export Selected (xlsx, csv, txt, docx)
Fully supportedThe Export Selected feature produces standard flat-file formats for any entity listing. We can consume these exports directly when migrating to platforms that accept CSV or spreadsheet imports, treating them as standard record sets with column headers.
| Object | Support | Notes |
|---|---|---|
| Entities | Mapping required | Entities are the core data objects in Rukovoditel — essentially user-defined database tables created via the Database Designer. Every installation has a different set of Entities, so we always introspect the actual entity list first and build a custom field map for each one. |
| Fields | Mapping required | Standard and custom fields are created per-Entity with a wide variety of types (text, number, date, entity reference, related records, users, user groups, MySQL query). Field IDs are numeric and unique per application, not globally consistent. We capture the full field definition including type, required flag, and validation rules during schema review. |
| Nested Entities (one-to-many) | Mapping required | Nested Entities represent one-to-many parent-child relationships and are implemented as separate tables with a foreign key back to the parent. We resolve this relationship and map it to the destination's equivalent (e.g., sub-tasks, child records) preserving the hierarchy at import time. |
| Related Records (many-to-many) | Mapping required | Many-to-many relationships use the Related Records field type, storing associations in a junction table. We extract the relationship table, map both sides of the association, and reconstruct it in the destination using that platform's native linking mechanism. |
| Users and User Groups | Mapping required | Rukovoditel Users and User Groups are separate objects tied to access control rules on Entities and Fields. We map user accounts to the destination's owner/assignee model and preserve group memberships as team or role assignments where supported. |
| Attachments | Mapping required | File attachments are stored on the server filesystem with references in the database. We export the binary files, preserve their record associations, and re-upload them to the target system's attachment storage. Inline images use the same path. |
| XML Export Templates | Mapping required | Rukovoditel's XML Export uses user-defined templates referencing fields by [field ID] notation. We parse the template logic to understand which fields are included and in what structure, then reconstruct equivalent field mappings for the destination import. |
| Export Selected (xlsx, csv, txt, docx) | Fully supported | The Export Selected feature produces standard flat-file formats for any entity listing. We can consume these exports directly when migrating to platforms that accept CSV or spreadsheet imports, treating them as standard record sets with column headers. |
Gotchas
What to watch for in Rukovoditel migrations
Issues we've hit on past Rukovoditel migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No native bulk export API endpoint
Every installation has a unique entity schema
SQL injection vulnerability history in v2.5.2
User authentication requires plaintext username/password for API
XML export templates must be manually configured
| Severity | Issue |
|---|---|
| High | No native bulk export API endpoint |
| High | Every installation has a unique entity schema |
| Medium | SQL injection vulnerability history in v2.5.2 |
| Medium | User authentication requires plaintext username/password for API |
| Low | XML export templates must be manually configured |
Leaving Rukovoditel?
Where Rukovoditel customers move next
5 destinations Rukovoditel can migrate to.
How a Rukovoditel migration works
Four steps, Rukovoditel-specific
Connect
API key + username/password (plaintext in request body) into Rukovoditel. Scopes limited to read-only on the data we move.
Map
We translate Rukovoditel-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Rukovoditel quirks before production.
Migrate
Full migration with Rukovoditel rate-limit handling. Rollback available throughout.
FAQ
Rukovoditel migration FAQ
Answers to the questions buyers ask most during Rukovoditel migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Rukovoditel migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther project management tools we support
Ready when you are
Migrate Rukovoditel.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Rukovoditel setup and destination — written quote back within a business day.