Migrate from Rukovoditel to Microsoft Project

Rukovoditel has no fixed Project object — any Entity can represent a project depending on how the customer configured it. During discovery, we identify which Entity functions as the project container by analyzing its relationship to other Entities (Nested Entity children, Related Records, and assignment fields). If multiple Entities represent sub-projects or work packages, they map to separate Tasks under a summary Task within a single Microsoft Project. The Entity name becomes the Project Name; any Entity date fields map to Project Start and Project Finish.

Nested Entities in Rukovoditel implement one-to-many parent-child relationships as separate database tables with a foreign key. These map directly to Microsoft Project Tasks under the parent Project or Summary Task. The Nested Entity's name becomes the Task Name, and its date fields map to Start and Finish. Duration is computed from date delta if the customer has Start and Finish fields; otherwise, the customer defines a default duration during scoping. WBS codes are assigned sequentially if no existing Rukovoditel hierarchy field exists.

Rukovoditel Field types (Text, Number, Date, Dropdown, User, User Group, Related Records) map to Microsoft Project Task Custom Fields scoped to the Task level. Text fields map to Text1-30, Numbers to Number1-10, Dates to Date1-10, and dropdown values to Outline Codes or Text fields with enumerated values. User and User Group assignments require a prior Resource mapping step because Microsoft Project Resources must exist before Task assignment Custom Fields can reference them.

Rukovoditel's Related Records field type stores many-to-many associations in a junction table. Microsoft Project has no native many-to-many object relationship model. We extract the junction table entries during discovery, then decide on a per-field basis: simple associations with a small set of values become Text or Outline Code Custom Fields with comma-separated values; complex associations with hundreds of possible values are documented in the handoff notes as a recommended SharePoint List or Power Automate flow to re-establish post-migration.

Rukovoditel Users map to Microsoft Project Resources. We extract all unique User records, resolve their email addresses and names, and create Resource records in Microsoft Project. The resource type (Work, Material, or Cost) is determined during scoping based on whether the user is a human assignee or a cost line item. If Rukovoditel User Groups exist and the customer uses group-level assignments, we create Resource Groups in Microsoft Project and assign each User Resource to its group.

Rukovoditel User Group records become Microsoft Project Resource Groups. We map the group membership during discovery and create Resource Groups in the destination project plan. If a User Group represents a department or team (rather than a security role), the Resource Group provides the grouping structure for resource utilization reporting.

Rukovoditel records can have a User or User Group assigned as a field value on any Entity. We extract all assignment records, resolve the assigned User to the mapped Resource, and create Microsoft Project Task Assignments with the appropriate Units percentage. If the original Rukovoditel assignment does not include time or effort data, Units defaults to 100% for a full-time assignment. The customer defines effort-driven versus duration-driven scheduling during scoping.

Rukovoditel stores file attachments on the server filesystem with database references. We export binary files, preserve their record associations, and upload them to a shared location accessible from Microsoft Project (SharePoint Document Library, OneDrive for Business, or the local file share the customer's team uses). We create Hyperlink Custom Fields on the corresponding Tasks pointing to the uploaded files. PDF and image attachments that represent visual deliverables become linked objects on the relevant Task.

Rukovoditel date fields on any Entity map to the corresponding Microsoft Project Task Start, Finish, or Deadline field. If the source Entity uses a custom date field named due_date, deadline, or target, we map it to the Deadline field. Constraints (Must Start On, Finish No Later Than) are applied only if the customer explicitly uses Rukovoditel date fields as hard constraints rather than scheduling inputs.

Rukovoditel Comments on Entity records migrate to Microsoft Project Task Notes fields. Notes are plain-text imports; rich-text formatting from Rukovoditel is preserved where the target field supports it, or stripped to plain text where it does not. If comments have timestamps or author attribution, we prepend this metadata to the Note body.