Migrate from Rukovoditel to Trello

Each distinct Rukovoditel Entity (created via Database Designer) maps to a Trello Board. During schema introspection we discover all Entities and identify the primary Entity representing Projects or Work Items. One Board is created per Entity, with the Board name sourced from the Entity's display name in Rukovoditel. If the customer has more than ten Entities, we recommend consolidating low-record-count Entities into Labels within a single Board rather than creating a separate Board for each.

Individual records in each Rukovoditel Entity map to Trello Cards. The Card title comes from the primary name field (the first text field defined in the Entity's configuration). All other record fields are mapped to Card fields, description, due dates, or custom fields depending on Trello plan. Records with a status field (e.g., New, In Progress, Completed) map to Trello Lists that we create on the destination Board to mirror the Rukovoditel workflow state.

Rukovoditel Nested Entities represent one-to-many relationships (e.g., a Project Entity with nested Task records). We map the Nested Entity to a Trello Card Checklist named for the child Entity, and each child record becomes a Checklist Item on the parent Card. If the Nested Entity itself has further nesting (grandchild records), we create a sub-checklist structure or note the depth limitation (Trello does not natively support checklist nesting beyond two levels).

Rukovoditel's Related Records field type creates many-to-many associations stored in a junction table. We extract the junction records and map them to Trello Card Links (one Card referencing another by Card ID) or to Labeled groupings if the relationship is categorizational rather than hierarchical. The customer selects the strategy during scoping. Many-to-many relationships with more than ten associated records per side are flagged as potential information-loss risks.

Rukovoditel Users map to Trello Board Members. We resolve each Rukovoditel user by email address and invite them to the corresponding Trello Board. Rukovoditel User Group memberships map to Board Labels (e.g., a Rukovoditel group 'Engineering' becomes a Label named 'Engineering' on the Trello Board). Users without a Trello account receive an email invitation during migration; migration cannot proceed past the user-mapping phase if the customer has not provisioned Trello accounts.

Rukovoditel User Groups (used for access control and organizational tagging) map to Trello Labels on Cards. We preserve the group name as the Label name and assign the Label color. If the customer has more than 25 distinct User Groups, we consolidate them into a smaller set of top-level Labels and document the full grouping in the migration map.

Rukovoditel stores file attachments on the server filesystem with database references. We extract the binary files, preserve their record associations, and re-upload them to Trello Cards via the Trello API. The 10MB file size limit on Trello Free and 250MB limit on Standard+ are enforced during export; files exceeding the destination plan limit are flagged and held in a separate queue for the customer to resolve (either upgrade Trello plan or remove oversized files from scope).

Rukovoditel fields of type 'Users' (which assign a specific user to a record) map to Trello Card Members. We resolve the Rukovoditel user ID to the corresponding Trello member account and assign them to the Card at migration time. Records with no assigned user are imported without a member assignment.

Rukovoditel date fields map to Trello Card due dates. The first date-type field in each Entity is treated as the primary due date; additional date fields map to Card custom fields (Standard+ plan required). We preserve the original date value and timezone information from Rukovoditel.

Rukovoditel long-text fields and description fields migrate to Trello Card descriptions. Rich text formatting in Rukovoditel is preserved as plain text or converted to Trello-compatible markdown where possible. HTML-formatted content from Rukovoditel is stripped to plain text to avoid rendering issues in Trello.

Rukovoditel numeric and currency fields migrate to Trello custom fields of type Number or Currency. This requires the Standard+ Trello plan; Free-plan migrations map numeric fields to Card description text instead and flag the plan requirement. We preserve the original field name as the custom field label.

Rukovoditel entity reference fields (which point to a single related record in another Entity) map to Trello Card Links or Card attachment references. We resolve the referenced record to its migrated Card ID and create a link on the source Card. If the referenced record has not yet been migrated (cross-phase dependency), we hold the reference and resolve it during the delta pass.