> ## Documentation Index
> Fetch the complete documentation index at: https://learn.nextedy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate from Risksheet to Powersheet

> Transition an existing Risksheet project to Nextedy POWERSHEET, converting your data model, sheet configurations, and document bindings to the Powersheet platform.

export const LastReviewed = ({date}) => {
  if (!date) return null;
  const formatted = new Date(`${date}T00:00:00Z`).toLocaleDateString("en-US", {
    year: "numeric",
    month: "long",
    day: "numeric",
    timeZone: "UTC"
  });
  return <p className="mt-10 text-sm text-gray-400 dark:text-zinc-500 not-prose">
      Last reviewed on {formatted}
    </p>;
};

## Before You Start

Risksheet and Powersheet share the same underlying architecture and data model concepts. The migration primarily involves moving configuration files to new locations and updating document references. Your existing Polarion work items, link roles, and custom fields remain unchanged.

<Tip title="Start with a test project">
  Create a copy of your project (or use a sandbox project) and perform the migration there first. Validate everything works before migrating your production project.
</Tip>

<Steps>
  <Step title="Install Powersheet">
    Ensure Powersheet is installed and licensed on your Siemens Polarion ALM server. See [Installing Powersheet](/powersheet/getting-started/installation) for details.

    After installation, verify that the **Administration > Nextedy Powersheet** menu section is available.
  </Step>

  <Step title="Migrate the Data Model">
    Risksheet data models define entity types with `workItems` arrays and `relationships`. Powersheet uses the same YAML structure with an updated format.

    1. Locate your existing Risksheet model YAML (typically in `.polarion/nextedy/models/` or `.polarion/models/`)
    2. If the model is in `.polarion/models/`, move it to `.polarion/nextedy/models/` via SVN
    3. Open **Administration > Nextedy Powersheet > Models** and verify the model loads

    The key data model properties map directly:

    | Risksheet Property            | Powersheet Equivalent    | Notes                           |
    | ----------------------------- | ------------------------ | ------------------------------- |
    | `workItems[].name`            | `domainModelTypes` keys  | Entity type identifiers         |
    | `workItems[].type`            | `polarionType`           | Polarion work item type mapping |
    | `workItems[].properties`      | `properties`             | Entity properties               |
    | `relationships[].from` / `to` | Relationship definitions | Same syntax                     |
    | `relationships[].role`        | Link role                | Same link role references       |
    | `relationships[].cardinality` | Cardinality              | Same cardinality values         |

    If your model uses the legacy array-based entity format, convert it to the key-based format:

    **Before (array-based):**

    ```yaml theme={null}
    workItems:
      - name: Hazard
        type: hazard
        properties:
          - name: severity
            type: enum
    ```

    **After (key-based):**

    ```yaml theme={null}
    domainModelTypes:
      Hazard:
        polarionType: hazard
        properties:
          severity:
            type: enum
    ```

    <Info title="Verify in application">
      The exact conversion syntax depends on your Risksheet version. Some versions may already use the key-based format. Open the model in **Administration > Nextedy Powersheet > Models** to verify it parses correctly.
    </Info>
  </Step>

  <Step title="Create the Sheet Config Custom Field">
    If you do not already have the `nextedySheetConfig` custom field:

    1. Navigate to **Administration > Documents & Pages > Document Custom Fields**
    2. Create a new field:
       * **Id:** `nextedySheetConfig`
       * **Name:** Sheet Config
       * **Type:** Enum: Nextedy - Sheet Config
  </Step>

  <Step title="Migrate Sheet Configurations">
    1. Open **Administration > Nextedy Powersheet > Configurations**
    2. Create new configuration entries for each Risksheet view you want to preserve
    3. Copy the YAML content from your Risksheet configurations
    4. Adapt the column binding paths to use the Powersheet data model entity names

    A typical RTM sheet configuration in Powersheet:

    ```yaml theme={null}
    columnGroups:
      Risks:
        groupName: Risk Analysis
        groupStyle: orange

    columns:
      title:
        title: Hazard
        width: 250
        hasFocus: true
      severity:
        title: Severity
        width: 100
      riskControls.riskControl.title:
        title: Risk Control
        width: 200
        columnGroup: Risks
        multiItem: true

    sources:
      - id: hazards
        title: Hazards
        model: risk-model
        query:
          from: Hazard
        expand:
          - name: riskControls
            title: Risk Controls
    ```
  </Step>

  <Step title="Bind Documents to Configurations">
    For each document that previously used a Risksheet view:

    1. Open the document properties
    2. Set the **Sheet Config** field to the appropriate Powersheet configuration
    3. Save the document

    <Warning title="Data model must match configuration">
      Ensure the data model referenced by your sheet configuration defines all entity types and relationships used in column binding paths. Mismatched models cause columns to fail silently.
    </Warning>
  </Step>

  <Step title="Configure Powersheet Drive">
    Powersheet uses Powersheet Drive for sidebar navigation. Update the document query property if needed:

    ```
    com.powersheet.powersheetDocumentQuery=type:powersheet OR HAS_VALUE:templateDoc.KEY
    ```

    This determines which documents appear in the Powersheet Drive sidebar topic.
  </Step>

  <Step title="Validate the Migration">
    1. Open **Administration > Nextedy Powersheet > Models** -- confirm the data model loads
    2. Open **Administration > Nextedy Powersheet > Configurations** -- confirm sheet configurations are visible
    3. Open a migrated document -- confirm the Powersheet table view displays correctly
    4. Create a test work item to verify save operations work
    5. Check that link roles and relationships resolve correctly in the sheet

    You should now see the Powersheet table view rendering with your migrated data, columns, and relationships from the former Risksheet configuration.
  </Step>
</Steps>

## See Also

* [Creating Your First Data Model](/powersheet/getting-started/first-data-model) -- data model setup tutorial
* [Configure a Relationship](/powersheet/guides/data-model/configure-relationship) -- adjust relationships post-migration
* [Assign Configuration to Document](/powersheet/guides/sheet-configuration/assign-config-to-document) -- document binding details
* [Incremental Configuration Approach](/powersheet/getting-started/incremental-configuration) -- extend configurations gradually after migration

<LastReviewed date="2026-07-02" />