---
description: "What changes when Actian moves your organization from the previous version of AI Analyst: what was copied and what wasn't, read-only conversations, paused schedules, first sign-in and your new access."
---

# Moving from the previous version of AI Analyst

This page is for people whose organization Actian has moved from the previous version of AI Analyst to the current Actian AI Analyst. It explains what was copied, what wasn't, and what you need to do after the move. The app calls the previous version "the previous product". This page calls its web app "the previous app".

!!! note "Transitional page"
    This page describes the move as of October 2026 and applies only to organizations that Actian moves from the previous version.

!!! info "Availability"
    - **Who can do this:** Actian runs the move for your organization. You can't start it or lock the previous app yourself.
    - **Deployment:** Actian SaaS only.

## How the move works

- **One Workspace per previous organization.** Each organization you had in the previous version is copied into one [Workspace](../settings/workspaces.md) of your AI Analyst organization. Actian either adds it as a new Workspace in an existing organization or uses it as the default Workspace of a new organization. If you had several previous organizations, they can arrive as sibling Workspaces in one organization.
- **Workspace name.** Unless Actian chooses another name, the Workspace is named after your previous organization's production environment.
- **Production only.** Only the production environment is copied. Other environments are skipped. If there was more than one production environment, only the oldest one is copied.
- **A point-in-time copy.** The move copies what existed when it ran. Anything you change in the previous app afterwards stays there.

For an introduction to Workspaces, Capabilities and the other terms on this page, see [Concepts](concepts.md).

## What moved

| Item | What you get |
|---|---|
| **Data connections** | Your connections, including their credentials. Each one is marked as ready, but it was **not** tested during the move. Check each connection before you rely on it (see [Data source health monitoring](../connections/data-source-health-monitoring.md)). |
| **Semantic layer** | Models, relationships, glossary terms and metrics, with the changes described in [What changed in your semantic layer](#what-changed-in-your-semantic-layer). |
| **AI analysts** | Each analyst keeps its name, description and instructions (called "guidelines" in the previous version), and is deployed to everyone in the Workspace. Its access to semantic-layer Models is set from the previous grants. |
| **Conversations** | Each conversation keeps the questions, the answers people saw and a shortened version of the reasoning steps. Sharing (only the owner, or the whole organization) is kept. Migrated conversations are [read-only](#your-old-conversations-are-read-only). |
| **Saved charts** | Saved charts become saved chart [Artifacts](../agent/working-with-agents/artifacts.md). Each keeps its title, sharing, link-to-conversation setting and archived state. |
| **Scheduled insights** | Name, prompt, schedule and time zone are kept. Every schedule arrives [paused](#your-scheduled-insights-arrive-paused). |
| **People** | Everyone who was a member of the previous organization, plus anyone who owned a conversation or a schedule there. |

## What did not move

These items are not copied:

- CSV file uploads, and the previous version's ad hoc SQL data sources
- saved tables and reports (only saved charts move)
- Slack and Microsoft Teams installations and channel links (see [Slack and Microsoft Teams](#slack-and-microsoft-teams))
- API keys
- your plan and trial
- audit logs
- Inbox items, stars and feedback on answers
- Steward sessions and Steward memory
- version history
- non-production environments

Some individual items can also be skipped:

| Item | Skipped when |
|---|---|
| Data connection | Its stored credentials can't be read, or a connection with the same name already exists in the Workspace. |
| Model | Its data connection was not moved (for example, a CSV upload). Anything that depends on that model is skipped too. |
| Relationship | It is a many-to-many relationship. |
| Glossary term | It was synced from a data catalog. |
| Metric | Its default filter has no equivalent in the current product. |
| AI analyst | The Workspace already has an analyst with that name, or your plan's analyst limit is reached. |
| Conversation | It has no messages, or its analyst or owner could not be moved. |
| Saved chart | The chart type can't be converted (for example, radar charts), or its conversation was not moved. |
| Scheduled insight | Its schedule is invalid, its analyst is missing, or its owner could not be moved. |
| Person | They have no email address. Their conversations and schedules are skipped too. |

If something you expect is missing, contact Actian support (see [Getting help](getting-help.md)) and say what is missing and where you expected to find it.

## What changed in your semantic layer

- **Names are now snake_case.** Model, dimension, measure, filter and relationship names that were not already in snake_case (lowercase words joined by underscores) were renamed. If your analyst instructions mention the old names, update them.
- **Unknown types were replaced.** A dimension with a type the current product doesn't recognize becomes a text dimension. A relationship with an unknown type becomes many-to-one.
- **Some metric details may be missing.** Optional custom filters on a metric can be dropped. A metric can also lose a join that could not be mapped, or its time dimension when that dimension is not on a joined model. Review your important metrics.
- **Per-filter analyst access did not carry over.** Each analyst's access to Models was set from the previous grants, but grants on individual filters were not. Glossary access was mapped as follows: access to all terms stays unrestricted, an "include" tag list becomes access to only those groups, and an "exclude" tag list becomes access to all groups except those. See [Access Management](../agent/creating-an-agent/access-management.md).

## Your old conversations are read-only

Nobody can continue a migrated conversation, including its owner, the people it was shared with and Studio members. When you open one in Explorer, the message box is hidden and you see:

> This conversation was migrated from the previous product. You can read it, but you can't send new messages. Start a new conversation to keep asking.

To keep asking about the same topic, click **New task** in Explorer and ask your question again.

In Studio, under **AI Analysts** → your analyst → **Monitoring**, a migrated conversation has a lock icon. Hover over it to see **Migrated from the previous product. Read only.**

## Your scheduled insights arrive paused

Every migrated schedule is paused, so nothing runs until it is resumed.

1. In Explorer, open **Scheduled Insights**.
2. Find the schedule. Its status is **Paused**.
3. Click the play button (**Resume**) next to the status.

Only the schedule's owner sees it in their list and can resume it. If your plan limits the number of active schedules, you can't resume more than that limit allows.

If a schedule shows **Won't run**, its analyst is no longer available to you, so its runs are skipped. Ask your administrator to give you access to that analyst. See [Scheduled Insights](../agent/working-with-agents/scheduled-insights.md) for more about managing schedules.

## Signing in for the first time

How you sign in depends on your email address and whether you already had an AI Analyst account.

### Your email is on your organization's single sign-on domain

If your organization uses Enterprise SSO and your email address is on one of its domains, you are added as a pending member. Your access and migrated content are ready for you. Sign in through your company's single sign-on, and your first sign-in activates your account.

Until then, administrators see you in **Settings** → **Members** under **Waiting for first SSO sign-in**, marked **Not signed in yet**. A pending member takes up a Seat. If an administrator removes a pending member, content already migrated to that person stays.

### You already had an AI Analyst account with the same email

Your existing account is reused. You keep your current password and sign-in method, and you are added to the organization. Any organization-level access you already had is kept. In the migrated Workspace you receive the Capabilities listed under [What access you have now](#what-access-you-have-now).

### Everyone else

Actian creates a password sign-in for your email address. The password is generated automatically and you are not told it, and AI Analyst does not send an email when the account is created. Ask your administrator or your Actian contact how to complete your first sign-in.

After you can sign in, you can change your password: open **Settings** → **Security**, and under **Password** click **Send reset email**. See [Security](../settings/security.md).

!!! warning "Require SSO"
    If your organization turns on **Require SSO**, only Enterprise SSO can sign in. People whose email is not on an SSO domain then can't use their password sign-in until **Require SSO** is turned off or their email address moves to an SSO domain.

For general sign-in help, see [Access Actian AI Analyst](access-wobby.md).

## What access you have now

Access in AI Analyst is set per Workspace with Capabilities. After the move, you have these Capabilities in the migrated Workspace:

| In the previous version you were | Capabilities in the migrated Workspace | What this gives you |
|---|---|---|
| A Studio user or an administrator | **Edit** and **Manage members** (both include **Chat**) | Studio and Explorer |
| Anyone else | **Chat** | Explorer |

What the Capabilities mean:

- **Chat:** converse with Analysts and use saved prompts in this Workspace.
- **Edit:** author Analysts, the semantic layer, connections and Steward configuration in this Workspace.
- **Manage members:** add, remove and set Capabilities for members of this Workspace only.

Migrated people don't receive organization-level administration. If the move created a new organization, that organization starts without a customer administrator, so ask your Actian contact how organization administration will be set up for you. If it landed in an existing organization, that organization's administrators can change access in **Settings** → **Workspaces** (click **Members** on the Workspace's row) and in **Settings** → **Members**. See [Workspaces](../settings/workspaces.md) and [Members](../settings/members.md).

!!! note
    You may see an Actian staff account listed as an Administrator in **Settings** → **Members**. Actian can add this account when it runs the move.

## The previous app after the move

Locking the previous app is a separate step that Actian takes after the move. Moving your organization does not sign anyone out of the previous app by itself.

When Actian locks your previous organization:

- everyone's membership of that organization is removed
- active sessions in the previous app are ended, so people are signed out
- the organization can no longer be reached in the previous app

Your previous organization and its data are not deleted, but you can no longer reach them.

Until the lock, the previous app keeps working. Changes you make there are not copied to AI Analyst.

## Slack and Microsoft Teams

Slack and Microsoft Teams connections are not moved. To use them again, an administrator reconnects them in Studio under **Connections** (under **Channels**, choose **Slack** or **Microsoft Teams**), then links each channel to the analyst with the same name as before. See [Slack](../connections/messaging-apps/slack.md) and [Teams](../connections/messaging-apps/teams.md).

## Troubleshooting

| Problem | What to do |
|---|---|
| I can't send a message in an old conversation. | Migrated conversations are read-only. Click **New task** in Explorer and ask again. |
| A scheduled insight isn't running. | Migrated schedules arrive paused. The owner opens **Scheduled Insights** and clicks **Resume**. If it shows **Won't run**, the owner needs access to the schedule's analyst. |
| A model or metric based on a CSV upload is missing. | CSV uploads are not moved, so models built on them are skipped. Upload the file again (see [CSV files](../connections/connect-a-data-source/csv-files.md)) and recreate the model. |
| A model, dimension or relationship has a different name. | Names were converted to snake_case. Update any analyst instructions that use the old names. |
| A connection fails when an analyst queries it. | Connections were not tested during the move. Check the connection and update its credentials if needed. |
| I can't sign in with a password. | If your organization has **Require SSO** turned on, password sign-in is blocked. Ask your administrator. If your email is on your organization's SSO domain, sign in through single sign-on instead. |
| I only see Explorer, not Studio. | You were not a Studio user or an administrator in the previous version, so you received **Chat** only. Ask an administrator for **Edit** in the Workspace. |
| A Slack or Teams channel no longer answers. | Channel links are not moved. An administrator reconnects Slack or Teams and links the channel again. |

If you still need help, see [Getting help](getting-help.md).