Migrate from Rukovoditel to monday Work Management

Every Rukovoditel Entity discovered during schema introspection becomes a monday.com Board. We create one Board per Entity, preserving the Entity name as the Board title. The Board description carries the original Entity description for admin reference. Board columns are configured during migration to match the discovered Field types as closely as monday.com's column types allow.

Each Rukovoditel Field maps to a monday.com Column of the closest matching type. Text fields map to Text columns; number fields map to Number columns; date fields map to Date columns; user assignment fields map to Person columns; entity reference fields (Related Records type pointing to another Entity) map to Connect boards columns with cross-board lookups resolved at migration time. Fields with no direct monday.com equivalent (e.g., MySQL query fields) are flagged for admin review and mapped to Text or Dropdown columns as appropriate.

Each Rukovoditel record (row in an Entity table) becomes a monday.com Item on the corresponding Board. The record's display name (typically a configured Name field) maps to the Item name. Standard fields populate the Board columns by matching field ID to column ID. The Item is created before any Sub-items or related records are attached.

Rukovoditel Nested Entities implement parent-child relationships via a foreign key in a separate table. We resolve the parent record ID at migration time and create each child record as a monday.com Sub-item attached to the parent Item. The Sub-item inherits the same column structure as the parent Board for the child Entity.

Rukovoditel Related Records fields use a junction table to store many-to-many associations. We extract the junction table entries during the data extraction phase, then write the resolved Item IDs to a monday.com Connect boards column or Mirror column on the destination Board. We preserve the original relationship direction (which Entity is the source and which is the target) to avoid reversed links in monday.com.

Rukovoditel User accounts map to monday.com Team Members by email address. We resolve the migration user in monday.com before record import begins. Owner fields on Rukovoditel records (which store a User ID) populate the Person column in monday.com by matching the email of the assigned owner to the monday.com member. User Group memberships are not directly migratable to monday.com Teams, but we deliver a written map of User Group assignments for the admin to apply via monday.com Team management post-migration.

Rukovoditel User Groups are access-control constructs with no direct monday.com equivalent because monday.com manages permissions at the Board and Workspace level rather than at a named group level. We extract all User Group memberships, map them to monday.com Board-level access settings (Edit, Comment, View), and deliver a permissions matrix that the customer's admin applies manually post-migration.

Rukovoditel stores file attachments on the server filesystem with a reference path in the database. We export the binary files, validate them, and re-upload them to monday.com's file storage via the monday.com API, creating File column entries on the corresponding Items. File names and original upload timestamps are preserved. Large files (above monday.com's 250 MB per-file limit) are flagged for the customer's admin to host externally and link.

Rukovoditel XML Export templates define which fields are included in XML output using [field ID] notation. We parse each active XML Export template to identify the exact field set the customer has been using for reporting, then document the equivalent monday.com column configuration so the customer's admin can rebuild the same field visibility in the destination Board.

Rukovoditel's Export Selected feature produces flat-file exports for any Entity listing. We consume these exports directly when migrating to monday.com CSV import format, mapping each CSV column to the corresponding monday.com Board column by header name match. This is the fastest path for simple Entity migrations with no nested records or related-record dependencies.

Rukovoditel enforces access control at the Entity and Field level per User and User Group. monday.com manages permissions at the Board and Workspace level. We extract the Entity-level access rules from the Rukovoditel database and deliver a permissions mapping document that the customer's admin applies as Board-level access settings in monday.com.

Rukovoditel date fields (date, datetime) map to monday.com Date columns with the original timezone preserved. Where a Rukovoditel Entity has both a start date and end date field that together form a range, we configure these as a monday.com Timeline column (available on Standard and above) so that the range renders as a Gantt-style bar in monday.com views.