⚠️ Important: Ardoq is discontinuing the legacy Core and Discover experiences on 2 November 2026. Your organization (account) will automatically be transitioned to the New Ardoq Experience by this date.
What is going to happen?
On 8 April 2026, Ardoq introduced the New Ardoq Experience, a redesigned version of Ardoq built to make architecture easier to navigate, understand, and act on. It has two parts:
New Core Experience: a redesigned homepage, navigation, and modeling capabilities that give architects and admins faster access to insights, views, and data.
New Discover Experience: a rebuilt interface for contributors, giving them a simpler, more focused way to explore architecture data.
Both have been available to opt into since 8 April 2026. On 2 November 2026, Ardoq migrates fully to the new versions and discontinues the legacy interfaces. Any organization that hasn't enabled the new experience is migrated automatically.
Start with the section below to find out what you need to do to prepare for the migration.
ℹ️ Note: If your organization was created after 8 April 2026, the New Ardoq Experience is already enabled and none of this applies to you.
How do I know if my organization has migrated?
You can check your current status in My Organization > Admin > Organization settings > Features. If the New Core Experience and New Discover Experience are both enabled, your organization has fully migrated. If one or both are disabled, there are still steps to complete.
Your organisation falls into one of three situations:
Your toggles | What it means | What you need to do | Go to |
Neither is on
| Full migration required | Enable both (see setup guides below) | Core tasks, then Discover tasks |
New Discover Experience only | Partial migration | Enable New Core Experience only | Core tasks |
New Core Experience only | Partial migration | Enable New Discover Experience only | Discover tasks |
🍏 Migration: Transitioning to the new features is fairly straightforward. There is a bit of configuration to get set up properly with the new homepage and make sure permissions and viewpoints are configured correctly in Discover. For a smooth migration, we recommend you follow the Migration steps laid out in the sections below.
Please get in touch with our support or your Customer Success Manager (CSM) if you have further questions about the migration than what is covered in this article.
What's the main changes to expect?
On 2 November 2026, Ardoq removes the feature toggles in Organization settings > Features and transitions all remaining accounts to the New Ardoq Experience. The legacy interfaces stop being accessible at that point. Here is what you can expect:
New Core Experience
What's new for Admins, Writers, and Readers:
A homepage built as a starting point. Top cards give you a count and a quick action for the component types and workspaces that matter to your organization, with a pinned dashboard below them for the numbers you check most.
A new sidebar and top bar. Fewer clicks to the views, data, and settings you use daily.
Modeling in the view. Create and update components and references inside the visualization while you're working in it.
One Component Overview page. Overview, Fields, References, Viewpoints, and Styles tabs, so a single page covers looking something up, editing it, connecting it, and visualizing it.
Quick search and a command palette. Cmd+K or Ctrl+K searches components and assets from anywhere in the product.
New Discover Experience
What's new for Contributors:
Discover inside the core application. One platform for everyone, reached at yourorg.ardoq.com/app/discover, with navigation that matches what architects see.
Viewpoints built in the Visual Builder. Any Core viewpoint can be shared with business users, and Priority Viewpoints let you decide which one opens first for each component type.
A single permission model. Can view on an asset, granted to the whole organization, a user group, or named users, controls exactly what contributors reach.
The same views and styles as Core. Business users get the current visualizations, including newer ones like bubble charts, with your styling applied.
Standard URLs for sharing. Copy the URL from any report or dashboard and it works the same for every role.
An admin-configured home page. Set Quick Links, pinned assets, search filters, and branding in Organization settings, and choose whether Tasks and Data inventory appear in Discover home and Contributor navigation.
Relevant articles: Administrator Guide: The New Ardoq Discover Experience | Contributor Guide: Getting Started in the New Discover Experience
Core migration steps
Complete these if the New Core Experience toggle is off. They affect your Admins, Writers, and Readers.
1. Set up your homepage (required)
The new homepage replaces the asset library as your starting page. To configure it, go to Organization settings > Home settings, and go through each section to:
Set up your top cards and add a quick action to each.
Pin a homepage dashboard.
ℹ️ Note: The dashboard you pin must be shared with your entire organization, or most users won't see it.
⚙️ Tip: Build a dashboard for the homepage rather than reusing an existing one. The homepage works best as a launch pad, not a destination.
2. Scope your homepage cards (recommended)
Scope each card by workspace, filters, columns, and sorting so its count reflects only the records that matter, and Manage Data opens the inventory already filtered.
3. Add filters to your homepage dashboard (recommended)
Add dashboard filters so each user can narrow down to their own domain or portfolio, and text widgets to guide your users.
4. Review your Priority Fields (recommended)
Select the fields that matter to the widest group of users at Organization settings > Component overview. Those fields then appear first on the Component Overview page.
⚙️ Tip: Don't prioritize technical fields used in calculations. If you use the Ardoq Foundation solution, sensible defaults are already configured for common component types.
5. Check the result with user impersonation (recommended)
Go to My organization > Admin > Access control, select a user with the Reader or Writer role, and click View as user. Browse as they would, and check what they can see, what opens by default, and what's missing.
A banner shows who you're viewing as. Use Pause to make a change as yourself, then Resume to check it.
ℹ️ Note: Impersonation is view-only, so you'll see buttons you can click that won't do anything. Ardoq shows you the product exactly as your user sees it. You can't impersonate other admins or service accounts. The AI Assistant and ShiftX aren't available while impersonating.
Discover migration steps
Complete these if the New Discover Experience toggle is off.
1. Audit the legacy Discover viewpoints (required)
The new Discover works only with viewpoints built for the core Ardoq application. Legacy Discover viewpoints don't carry across, so any legacy viewpoint without a Core equivalent needs rebuilding in the Core Visual Builder. There's no automated transfer, as Legacy Discover and Core viewpoints don't have the same underlying structure. A Core viewpoint always defines a context component as the starting point, whereas Legacy can have multiple entry points.
This is a good time to take stock of your viewpoints. We recommend that you go over your legacy Discover viewpoints and note down your most important ones for top component types. Then start by recreating those.
ℹ️ Note: Check before you rebuild. Most organizations find most of their viewpoints already have a Core application equivalent.
See the full configuration guide: Administrator Guide: The New Ardoq Discover Experience
2. Check the viewpoint permissions (required)
The new Discover uses Core's granular permission model. Legacy Discover permissions do not carry over. Ensure contributors have the necessary access:
Viewpoint permissions: Users need Can view access on the viewpoint itself (granted to the whole organization, a group, or individual users via Viewpoints > Manage Permissions).
Workspace permissions: Users also need Can view access on the underlying workspaces; otherwise, the viewpoint opens without the related components.
Shared resources: Ensure proper viewing permissions are granted for any Dashboards, Reports, and Surveys linked in Discover or pinned as Quick Links.
ℹ️ Note: Viewpoints appear based on their starting component type. For example, a viewpoint starting from an Application only displays when viewing an Application component.
3. Review your Discover configuration (required)
Organization settings > Discover > General controls what appears on the Discover home page and in Contributor navigation. Organization settings > Discover > Branding controls your logo, homepage banner, and welcome message.
Your existing configuration, including quick links, carries over from legacy Discover, so nothing looks broken on day one. What's new is a set of controls that didn't exist before. Under Organization settings > Discover > General, you can show or hide Tasks and Data inventory independently on the Discover home page and in Contributor navigation. Worth a pass so contributors see only what's relevant to them.
4. Set your Priority Viewpoints (recommended)
Instead of showing every available viewpoint in the dropdown like in legacy Discover, priority viewpoints let you shortlist one or more viewpoints per component type.
Go to Organization settings > Component overview > [component type] > Viewpoints, select your priority viewpoints, then drag them into order. The viewpoint at the top is the one that opens by default.
Without this, users see Ardoq’s Default Overview viewpoint. They can still switch to anything else they have access to.
⚙️ Tip: Start with the two or three component types your business users open most. Applications and Business Capabilities are usually the right place to begin.
5. Check the result with user impersonation (recommended)
Go to My organization > Admin > Access control, select a real contributor, and click View as user. Browse Discover as they would, and check what they can see, what opens by default, and what is missing.
A banner shows who you're viewing as. Use Pause to make a change as yourself, then Resume to check it.
ℹ️ Note: Impersonation is view-only, so you’ll see buttons you can click that won’t do anything. Ardoq shows you the product exactly as your user sees it. You can’t impersonate other admins or service accounts. The AI Assistant and ShiftX aren’t available while impersonating.
More migration-related questions
We've enabled one of the new features but not the other. Does this apply to us?
Yes. Both need to be enabled for you to be fully migrated. On 2 November, the remaining features are enabled, depending on whichever one is still missing. Go to Organization settings > Features to check.
Your toggles | What it means | What you need to do | Go to |
Neither is on
| Full migration required | Enable both (see setup guides below) | Core tasks, then Discover tasks |
New Discover Experience only | Partial migration | Enable New Core Experience only | Core tasks |
New Core Experience only | Partial migration | Enable New Discover Experience only | Discover tasks |
Does enabling a toggle affect everyone immediately?
Yes. Feature toggles apply to your whole organization the moment they're switched on. There's no per-user or per-group targeting. If you have the option, we recommend that you test in a sandbox first and give your users notice.
Can we roll out in stages?
Until 2 November, yes. Enable the New Core Experience for your core users first, then the New Discover Experience for contributors once your team is comfortable. After the deadline, both are on. Start rolling out in stages before then.
What’s new since the 8 April launch?
Capability | What it solves |
Impersonation | Browse Ardoq as another user and verify what they see before you roll anything out. |
Priority viewpoints | Select the preferred viewpoint to open first for each component type, instead of Ardoq's Default Overview. |
Homepage data settings: filters, columns, and sorting | Tailor each card's Manage Data experience, scoping which records are counted, and set the filters, columns, and sorting for your end users. |
Cleaner Discover landing page | Hide Tasks and Data inventory from Discover home and from Contributor navigation, independently. |
Semantic quick search | Find components and assets by meaning across components, dashboards, reports, surveys, presentations, and broadcasts. |
ℹ️ Note: Semantic search is generally available but rolling out gradually. Contact your Customer Success Manager to move your organization up the queue.
To see all the Discover changes, you can follow the New Discover Changelog.
How long does setup take?
For most organizations, configuring the new homepage takes around 3 minutes.
The Discover setup involves a few additional migration steps depending on your viewpoint availability and current permissions. See the migration steps.
Will there be any downtime?
No. There's no maintenance window and no interruption to service. Where you will experience a bit of friction is getting everything configured.
Most importantly, to ease the transition for your business users, making sure you have permissions set up correctly.
Check your workspace permissions and make sure Contributors and other business users have access to the workspaces they need to see their application and business capabilities in Discover. Once that's in place, they can find and visualize your enterprise data straight away, before you've set up a single viewpoint.
Viewpoints are the next step, and the most cumbersome (sorry). Building them in Core, getting the permissions right, and configuring your Priority fields and Priority viewpoints is the most time-consuming part of the transition. How long it takes depends on how many viewpoints you have or want to recreate in Core Ardoq.
⚙️ Tip: We recommend using this migration as an opportunity to curate your library. Sharing a limited, relevant set of viewpoints can provide a more effective experience for business users than migrating your entire legacy catalog.
Will we lose any data?
No data or assets are lost, except for Legacy Discover viewpoints. All assets, components, references, workspaces, views, fields, surveys, broadcasts, and integrations remain unaffected.
New Discover only works with viewpoints built for the core Ardoq application, so any legacy Discover viewpoint still relies on a Core equivalent built in the Core Visual Builder.
See the Discover tasks above and the Administrator Guide: The New Ardoq Discover Experience for the difference between the two.
Who needs to do this work?
Every task above requires Admin access.
What if we do nothing at all?
On 2 November, your organization will automatically transition to the New Ardoq Experience. No data will be lost or modified, and sensible defaults will apply immediately across all features.
If you take no action beforehand, the default setup will result in the following key changes:
Legacy Discover Viewpoints: Unconverted legacy viewpoints will no longer be available. Contributors will only see viewpoints built in Core that they have permission to view.
Workspace Permissions: Access is controlled via Core workspace permissions rather than Discover viewpoint settings.
Default Landing Views: Ardoq's Default Overview viewpoint will open for all component types unless Priority Viewpoints are configured.
Updated URLs and Redirects: Discover moves to
yourorg.ardoq.com/app/discover. Legacy links and bookmarks will automatically redirect to their closest equivalent.
Where your old links land
Legacy Discover URL | Redirects to |
|
|
|
|
|
|
|
|
|
|
Anything else under |
|
ℹ️ Note: Ardoq removes the feature toggles on 2 November, so there's no way back to the legacy experience. You can still complete every task above afterwards.
More questions?
Please get in touch with our support or your Customer Success Manager (CSM) if you have further questions about the migration than what is covered in this article.
Available Resources
Admin & Migration Guides
Feature & Core Guides
Discover & Contributor Guides
For detailed setup instructions, troubleshooting, and full feature guides, explore the resources listed above.