AplasAplas Docs

Moving to the new Aplas

For organizations moving from the earlier version of Aplas to the new one: what stays the same and what changes

Aplas has been rebuilt. Organizations created since August 2026 use the new version, and every organization on the earlier version is being moved to it. This page is for the owners, admins and architects of an organization that is about to move, or has just moved.

The move is something we do for you. It takes a few minutes to under an hour, and your organization keeps its address, its members and its published pages.

The earlier version receives no new features. All new work goes into the new version, which is why every organization moves.

What you need to do

For most organizations, nothing. Two cases need action on your side:

If you haveWhat to doWhen
Scripts that call the REST APIPoint them at the newer API, /api/v3. Your existing keys work there. See Scripts and the API.Ready for the day of the move
A LeanIX or Confluence connectorNothing before the move. Afterwards we check the workspace with you and start the connector again.After the move

On the day, ask your members to stop editing while the move runs. People can still view throughout; saving is paused until it finishes. Anyone who left the studio open in a browser tab should open it afresh afterwards.

What stays the same

  • Your organization. The same address. An organization that pays for Aplas keeps its plan and its price.
  • Your members and their roles. Everyone signs in the way they do today.
  • Your published pages. Every publication that moves keeps its address and its audience, so links you have shared keep working.
  • Your map. It arrives pinned where it is today, with its styles. Region outlines are redrawn and some roads may take a different path between the same systems.
  • Your data. Applications, integrations, components, collections, tags, custom fields and comments all come across.
  • Your API keys. The keys do not change. The API they call does: see below.

What the earlier names become

Earlier versionNew version
IndexA workspace, holding your inventory. Each index becomes a workspace with the same name.
Application, integration, componentAssets of the built-in type of the same name. Integrations still draw as roads on the map. A component whose name or tags mark it as a technology becomes a technology asset.
TagsAssets of the Tag type. The tag group your map uses for its regions becomes a set of business-unit assets, so the regions are real things in your inventory.
CollectionA business process, an initiative or a collection, depending on its name, its tags and whether it is ordered. A business process keeps its steps in order.
Custom fieldsFields on the asset type. A rating with named options becomes a choice field.
MapA map view.
StyleA style on that map view.
PublicationA published view. Published lists everything that is live.

Your migration report lists anything that had to be renamed or could not be converted, by name. Ask us for it.

What is new

  • Asset types are yours. Add business capabilities, processes, data objects, technologies, teams or types of your own, each with its own fields and relations to the applications you already have. See Inventory.
  • More views of the same inventory. Table, matrix, graph, flow and search sit beside the map. See Views.
  • Publish any view, export any table. See Publishing and Exports.
  • An assistant that builds the inventory with you. It proposes; nothing is written until you confirm. See Assistant.
  • Your own AI tools can read the inventory. The MCP server works for your organization once it has moved. See AI setup.

The free plan

The earlier free plan, on which everything an organization published was open to anyone on the internet, is no longer offered. The new Free plan is private and covers 50 assets and one workspace. If your organization was on the earlier free plan, every published page that moves stays open to the readers it already had.

Published pages

People who open your published pages find them at the same addresses, looking much as they did.

  • A published map keeps its look. Selecting an application still opens a panel with its fields, integrations, collections, components, history and comments.
  • A published style keeps its style.
  • A published search page becomes a search view at the same address.

Scripts and the API

The earlier REST API, /api/v2, describes the earlier model. Once your organization has moved, it answers every call with 403 and a message naming the newer API.

  • Move your scripts to /api/v3. The same API key works. The API reference describes each endpoint.
  • The shapes are different. /api/v3 speaks in workspaces, asset types, assets and relations. A script written for /api/v2 needs its calls rewritten, not only its address changed.
  • Send the key as Authorization: Bearer <key>. This is the only accepted form on both APIs. The older api_key header is not read.

Connectors

  • LeanIX and Confluence connectors move with you, including the login they use. Each one arrives paused. We start it after checking the workspace with you. A LeanIX connector's first sync recognises the assets that are already there, so nothing arrives twice. A Confluence page linked to an asset by an id kept from the earlier version is matched to that asset. Any other page is matched by name, ignoring capitals and surrounding spaces, to an asset of the type the connector maps it to that no other page has already claimed. A page that does not match exactly one such asset arrives as a new one, which can duplicate an existing asset.

See Connectors for how connectors work in the new version.

See it before you move

If your organization pays for Aplas, we tell you the date in advance and make a private copy of your organization in the new version, at https://app.aplas.com/{your-organization}-v2. Owners and admins can sign in to it.

Use it to check three things:

  1. Your maps look as you expect.
  2. Your inventory counts match.
  3. Your published pages show what their audience should see.

Changes made in the copy are not kept. Keep working in your own organization until the move.

An organization on a trial is moved straight away, with no advance date and no copy to review, and is told on the day.

If something is wrong afterwards

Tell us. For a short time after the move we can return an organization that pays for Aplas to how it was before, with its pages and their settings restored. Work done in the new version in between would be lost, so say so early. An organization that has changed to one of the new plans since the move cannot be returned.

Getting help

Reply to the email that told you about the move, or write to support@aplas.com.

On this page