Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Integration Service

Migrate from AIS on-prem installation to hybrid installation

Migrate from AIS on-prem installation to hybrid installation

  • Last UpdatedJul 30, 2026
  • 3 minute read

This section guides you to transition from a fully on-premises AVEVA Integration Service (AIS) deployment to a Hybrid Installation.

This process integrates the locally installed AIS with the AVEVA Integration Service Data API and AVEVA Integration Service Config API hosted on CONNECT.

Steps to migrate

Follow the steps below to ensure a smooth migration:

  1. Subscribe to AIS CONNECT Service Contact AVEVA Support to subscribe to the AVEVA Integration Service on CONNECT.

  2. Install AIS Locally in Hybrid Mode Install AVEVA Integration Service on your local network using Hybrid Installation mode.

  3. Integrate with CONNECT Configure the locally installed AIS to communicate with the AVEVA Integration Service Data API and Config API hosted on CONNECT, using a CONNECT Token and Hybrid mode configuration.

  4. Recreate Data Sources Existing Data Sources from your on-premises installation will not be automatically migrated to the CONNECT-hosted AIS. Data Sources must be created manually or contact AVEVA Support to arrange an automated migration.

  5. Manage Users in CONNECT Transition user management to CONNECT and assign appropriate roles.

    Note: Use the same Data Source naming conventions as per your on-premises deployment to avoid disruption to existing integrations.

This process ensures a seamless transition from a local AIS deployment to the CONNECT-hosted counterpart, while maintaining integration configurations and Data Source settings.

Integrating the Local AIS Server with CONNECT

A locally installed AIS Server must be linked to the AIS CONNECT Service to enable live data pull from Data Sources.

  • For subscription requirements, refer to Who Should Subscribe to AVEVA Integration on CONNECT.

  • For installation guidance, refer to Deploying Hybrid AVEVA Integration Service.

Installing AIS in Hybrid mode automatically establishes the integration between the local AIS Server and AIS CONNECT Service, enabling live data pull via the CONNECT-hosted Data API.

Integrating AVEVA Applications with AIS CONNECT

AVEVA applications such as Unified Engineering (Compare & Update), ERM Integration, and Gateway Interface can be integrated with the CONNECT-hosted AVEVA Integration Service. To use these interfaces, you must have access to the AIS Cloud service.

Follow the steps below to configure this integration:

  1. Install and Configure AIS in Hybrid Mode

    Ensure that AVEVA Integration Service is installed using the Hybrid Installation option and fully configured. Refer to the AIS Installation and Configuration Guide for detailed instructions.

  2. Update the AIS Endpoint URL

    In your AVEVA application configuration, update the AIS URL to point to the CONNECT-hosted Data API endpoint.

    Example (EU region): https://eu.ais.connect.aveva.com/data

    Note: Integration with the cloud-hosted AIS requires a LaaS or L4S licence. The ALS licence type is not supported for cloud integration.

  3. Create a Service Application (Client ID & Client Secret)

    Create a Service Application (Client ID and Client Secret) for the AVEVA application — for example, AVEVA ERM — to authenticate with AIS CONNECT.

    • Assign the Data Source Admin role to the Service Application within AIS.

    • Share the Client ID and Client Secret with the relevant application owner (e.g., ERM Infrastructure Owner) to configure their environment.

    • Ensure the Data Source Admin role is confirmed and active on the client.

  4. Generate a Service Access Token for AIS Local Server

    Generate a Service Access Token via the CONNECT portal to allow the local AIS Server to communicate with the AIS SaaS component.

    • Select the Data Source Admin role when generating the token.

    • Access the AIS Web Administration interface.

    • Register the generated Service Access Token to establish the link between the local AIS Server and the AIS SaaS (CONNECT-hosted) component.