--- sourceDocument: zurich Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/delta-xanadu-zurich Release : - zurich ft:locale : - en-US ft:publication_title : - zurich Combined Product Files ft:clusterId : - delta3zx bundleId : - delta3zx --- # Combined Service Exchange release notes for upgrades from Xanadu to Zurich # Combined Service Exchange release notes for upgrades from Xanadu to Zurich {#ariaid-title1} Release version: Zurich Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 10 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Combined Service Exchange Release Notes for Upgrades from Xanadu to Zurich This consolidated release notes document covers the progression and upgrade guidance for Service Exchange from the Xanadu release through to Zurich. It is designed to help ServiceNow customers prepare for and execute upgrades with clear instructions on migration, compatibility, and new capabilities. The notes address important upgrade prerequisites, feature introductions, changes, deprecations, and activation procedures relevant to Service Exchange across multiple platform versions. Show full answer Show less ## Upgrade Guidance and Compatibility * **Legacy Migration:** Customers using Service Exchange (Legacy) versions must migrate their configuration data before upgrading to newer releases using the Migration Utility documented in KB1499823. * **Version Compatibility:** From Xanadu onward, mismatched version support allows providers and consumers to run different Service Exchange versions; however, new entitlements require both parties to upgrade to activate them. * **Simultaneous Upgrades:** When using Service Exchange for Providers and Consumers on the same instance, both applications must be upgraded simultaneously to maintain compatibility. * **Deny ACLs Installation:** Post-upgrade to Yokohama or Zurich, if upgraded to specific Service Exchange and Sales CRM plugin versions beforehand, customers need to run a Repair on the Service Exchange application to install Deny ACLs properly. * **Global Script Include:** Automatically installed or updated during Service Exchange application installation on supported platform versions (Washington DC Patch 9, Xanadu Patch 4, Yokohama, and Zurich). ## Key Features Introduced Across Releases * **Xanadu:** Mismatched version support enabling independent upgrades for providers and consumers; configuration revisions allowing parallel use of old and new entitlement versions; consumer pre-flows for approval and control before synchronization; integration with Sales Customer Relationship Management for quick ordering via remote record producers. * **Yokohama:** Enhanced provider control with remote catalog item client scripts and UI policies; ability to copy local catalog items as remote record producers; automatic transform mapping generation using Now Assist (leveraging AI); consumer variable sets for better customization of remote record producers. * **Zurich:** Foundation data sync for scheduled sharing of foundational data types (CMDB, assets, users, groups, etc.) to reduce manual efforts; improved journal field framework with named user entries and synchronization for accountability; new flow actions preserving flow compatibility across entitlement revisions; magic links for seamless cross-instance user access without manual logins. ## Changes and Deprecations * **Theme Update:** Zurich introduces the Coral theme as the new default for portals and mobile/web experiences, featuring a fresh and brand-neutral look with an optional dark theme. * **Deprecation:** The Service Exchange (Legacy) applications for Providers and Consumers are deprecated and unsupported for new activations. Customers must migrate to the latest Service Exchange applications as per KB1499823. * **No removals or other feature deprecations** were noted between Xanadu and Zurich beyond legacy versions. ## Activation and Additional Considerations * Service Exchange must be installed by requesting it from the ServiceNow Store. This applies consistently from Xanadu through Zurich. * No new browser, accessibility (other than the dark theme option), localization, or additional requirements were introduced beyond those noted with the Coral theme in Zurich. ## Practical Outcomes for ServiceNow Customers * Upgrading following these notes ensures uninterrupted service exchange between providers and consumers, even if they are on different versions temporarily. * Migration utilities and upgrade guides provide a clear path to move from legacy versions to supported releases, preserving configuration and entitlement integrity. * New features improve control, automation, and user experience, including data synchronization, entitlement management, catalog item handling, and user access. * The updated theme and accessibility options enhance usability in the Zurich release. * Customers can expect smoother data exchange workflows, increased security with Deny ACLs, and enhanced collaboration capabilities between provider and consumer instances. Consolidated page of all release notes for Service Exchange from Xanadu to Zurich. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Service Exchange release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Xanadu to Zurich. Tip: If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release." ## Important information for upgrading Service Exchange to Zurich Before you upgrade to Zurich, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-serviceexchange-summary__entry__2} | Release | Release notes | |-|-| | Xanadu | * Service Exchange 2.x.x that is being released with the Xanadu release does not support migration of the Service Exchange (Legacy) versions. If you are using a Service Exchange (Legacy) version, before you upgrade to the Xanadu release, you must follow instructions in the [Service Exchange for Providers (Legacy) - Migration Utility (KB1499823)](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1499823) article in the Now Support Knowledge Base to migrate your configuration data. * If you are upgrading from version 1.x.x of Service Exchange, follow the steps listed in [Upgrade Guide - Service Exchange for Providers and Consumers application (v2.x.x release - KB1700387)](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1700387) to migrate your Service Exchange applications. * Due to the introduction of mismatched version support, new entitlements cannot be activated until both the consumers and providers upgrade to the Xanadu release. Older active entitlements will continue to work but new ones cannot be activated. | | Yokohama | Upgrade information : * When using Service Exchange for Providers and Service Exchange for Consumers in a single instance, you must upgrade both applications simultaneously to the same version to maintain compatibility. * The Service Exchange Global Script Include is automatically installed or updated when you install the Service Exchange application on the following platform versions: * Washington DC Patch 9 * Xanadu Patch 4 * Yokohama * Service Exchange 2.x.x, which was first released with the Xanadu release, does not support migration of Service Exchange (Legacy) versions. If you are using a Service Exchange (Legacy) version, before you upgrade to the Yokohama release, you must follow instructions in the [Service Exchange for Providers (Legacy) - Migration Utility \[KB1499823\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1499823) article in the Now Support Knowledge Base to migrate your configuration data. * If you are upgrading from Service Exchange version 1.x.x, follow the steps in [Upgrade Guide - Service Exchange for Providers and Consumers application (v2.x.x release) \[KB1700387\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1700387) to migrate your Service Exchange applications. * Due to the introduction of mismatched version support, new entitlements cannot be activated until both the consumers and providers upgrade to Service Exchange version 2.x.x. Older active entitlements will continue to work but new ones cannot be activated. * If you upgrade to Service Exchange version 2.0.55 with Sales Customer Relationship Management plug-in version 1.0.4 before upgrading the platform to the Yokohama release, the new Deny ACLs will not be installed. To ensure the Deny ACLs get installed, after upgrading to Yokohama, you must click Repair to reinstall the Service Exchange application. | | Zurich | Upgrade information : * Service Exchange version 2.x.x: Which was first released with the Xanadu release, doesn't support migration of Service Exchange (Legacy) versions. Service Exchange (Legacy) version: Before you upgrade to the Zurich release, follow instructions in the [Service Bridge for Providers (Legacy) - Migration Utility \[KB1499823\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1499823) article in the Now Support Knowledge Base to migrate your configuration data. * Service Exchange version 1.x.x: When upgrading, follow the steps in the [Upgrade Guide - Service Bridge for Providers and Consumers application (v2.x.x release) \[KB1700387\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1700387) article in the Now Support Knowledge Base to migrate your Service Exchange applications. * Service Exchange version 2.x.x: Due to the introduction of mismatched version support, new entitlements can't be activated until both the consumers and providers upgrade to Service Exchange version 2.x.x. Older active entitlements continue to work but new ones can't be activated. * When you upgrade to Service Exchange version 2.0.55 with Sales Customer Relationship Management plug-in version 1.0.4, before upgrading the platform to the Zurich release, new Deny ACLs aren't installed. To ensure the Deny ACLs get installed, after upgrading to Zurich, select Repair to reinstall the Service Exchange application. * When using Service Exchange for Providers and Service Exchange for Consumers in a single instance, you must upgrade both applications simultaneously to the same version to maintain compatibility. * When you install the Service Exchange application, the Service Exchange Global Script Include is automatically installed or updated on the following platform versions: * Washington DC patch 9 * Xanadu patch 4 * Yokohama * Zurich | [ ] ## New features Between your current release family and Zurich, new features were introduced for Service Exchange. {#dfrn3-serviceexchange-summary__entry__10} | Release | Release notes | |-|-| | Xanadu | [Service Exchange mismatched version support](https://www.servicenow.com/docs/access?context=service-bridge-v2-mismatch-version&family=xanadu&ft:locale=en-US) : Providers and consumers can run different versions of the Service Exchange applications without affecting their ability to exchange data. Providers can adopt new features without coordinating their application upgrades with their consumers. [Configuration revisions](https://www.servicenow.com/docs/access?context=service-bridge-v2-config-revision&family=xanadu&ft:locale=en-US) : Providers can develop and deploy new versions or revisions of entitlements with updated functionality to compatible consumers without affecting consumers who have not updated their application. Consumers can therefore use older revisions of entitlements including remote task definitions, remote record producers, and foundation data sync offerings while deploying new revisions. [Consumer pre-flows](https://www.servicenow.com/docs/access?context=service-bridge-v2-conf-consumer-flow&family=xanadu&ft:locale=en-US) : Consumers can control data synchronization with their providers by associating a flow with a Service Exchange remote record producer and run consumer-defined processes, such as approvals, before a task is synchronized to their provider. [Integration with Sales Customer Relationship Management](https://www.servicenow.com/docs/access?context=service-bridge-v2-omt-intg&family=xanadu&ft:locale=en-US) : Providers can enable customers to quickly order entitled Sales Customer Relationship Management product offerings from their service catalog by publishing them as remote record producers on consumer instances. | | Yokohama | [Remote Catalog Item Client Scripts](https://www.servicenow.com/docs/access?context=service-bridge-v2-add-scripts-to-rrp&family=yokohama&ft:locale=en-US) : Provider: Perform more complex tasks and gain better control over the completeness and correctness of catalog requests from the consumer by including catalog client scripts, UI Policy scripts, and other common scripts that consumers can choose to include for Remote Catalog items. [Copy From Service Catalog Item to Remote Catalog Item](https://www.servicenow.com/docs/access?context=service-bridge-v2-copy-catalog-as-rrp&family=yokohama&ft:locale=en-US) : Providers: Eliminate the need to re-create catalog items manually in the Service Exchange remote catalog by copying single and multiple catalog items through the UI to remote record producers that can be synchronized to the consumer instance. [Transform Mapping Assist](https://www.servicenow.com/docs/access?context=now-assist-tmt-exploring&family=yokohama&ft:locale=en-US) : Providers: Streamline the transformation mapping process and reduce errors by generating transform mappings between provider and consumer tables automatically using the Transform Mapping Assist feature that leverages the NOW large language model (LLM). [Consumer Variable Sets](https://www.servicenow.com/docs/access?context=service-bridge-v2-consumer-variables&family=yokohama&ft:locale=en-US) : Consumers: Manage requested content and flow better by adding additional variables to add customization to your remote record producers. | | Zurich | [Foundation data sync](https://www.servicenow.com/docs/access?context=service-bridge-v2-explore-foundation-data-sync&family=zurich&ft:locale=en-US) : Reduce manual effort, and eliminate the need to share data externally by sharing selected foundational data types with your consumers on a scheduled cadence. This data transfer supports the service life cycle by providing foundational data context for operational workflows. The supported tables are CMDB (CIs), CMDB Relationship, Asset, User, Group, Location, Company, and Department. [Journal field framework](https://www.servicenow.com/docs/access?context=service-bridge-v2-expolre-journal-field-framework&family=zurich&ft:locale=en-US) : * Write journal entries as a named user instead of using a generic company name to enhance authenticity and accountability. * Maintain a complete historical record across instances by synchronizing previous journal entries between provider and consumer instances. * Ensure that all critical operational updates remain current by mapping and synchronizing any journal-type field between provider and consumer instances. [Flow action](https://www.servicenow.com/docs/access?context=service-bridge-v2-flow-action&family=zurich&ft:locale=en-US) : Ensure that Remote Tasks and Remote Record Producers continue to function correctly as you adopt newer revisions by maintaining flow compatibility across configuration revisions using four new Flow Actions that preserve mapped variable integrity. [Magic links](https://www.servicenow.com/docs/access?context=service-bridge-v2-explore-magic-link&family=zurich&ft:locale=en-US) : Convert regular links sent from a provider instance into magic links that enable consumer users to directly access the linked resource in the provider instance without having to manually log in. | [ ] ## Changes Between your current release family and Zurich, some changes were made to existing Service Exchange features. {#dfrn3-serviceexchange-summary__entry__18} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | Coral theme : Coral is now the default theme for new portal, web, and mobile experiences with Next Experience or Core UI enabled. This theme provides a fresh look and feel, featuring brand-neutral illustrations to enhance your user experience. A dark theme option is available for web and mobile experiences. | [ ] ## Removed Between your current release family and Zurich, some Service Exchange features or functionality were removed. {#dfrn3-serviceexchange-summary__entry__26} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Deprecations Between your current release family and Zurich, some Service Exchange features or functionality were deprecated. {#dfrn3-serviceexchange-summary__entry__34} | Release | Release notes | |-|-| | Xanadu | * Service Exchange (legacy) application is now deprecated and no longer supported or available for new activation. The Service Exchange for Consumers application provides the latest experience for this functionality. * Service Exchange for Providers (legacy) application is now deprecated and no longer supported or available for new activation. The Service Exchange for Providers application provides the latest experience for this functionality. See [KB1499823](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1499823) for details on migrating from the legacy version. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Activation information Review information on how to activate Service Exchange. {#dfrn3-serviceexchange-summary__entry__42} | Release | Release notes | |-|-| | Xanadu | Install Service Exchange by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=xanadu&ft:locale=en-US). | | Yokohama | Activation information : Install Service Exchange by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=yokohama&ft:locale=en-US). Important: Service Exchange is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | | Zurich | Activation information : Install Service Exchange by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=zurich&ft:locale=en-US). Important: Service Exchange is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | [ ] ## Additional requirements If any additional requirements were introduced or changed for Service Exchange we have noted them here. {#dfrn3-serviceexchange-summary__entry__50} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for Service Exchange we have noted them here. {#dfrn3-serviceexchange-summary__entry__58} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for Service Exchange, such as specific requirements or compliance levels. {#dfrn3-serviceexchange-summary__entry__66} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | Accessibility information : Dark theme : The new Coral theme includes a dark theme option for web and mobile experiences. This option is commonly used to alleviate eye strain and improve readability. | [ ] ## Localization information If there are specific localization considerations for Service Exchange we have noted them here. {#dfrn3-serviceexchange-summary__entry__74} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for Service Exchange we have noted them here. {#dfrn3-serviceexchange-summary__entry__82} | Release | Release notes | |-|-| | Xanadu | * Enable providers to adopt new features and provide uninterrupted service to their consumers who have not upgraded. * Assess entitlements for compatibility before syncing them to consumers. * Enable consumers to run specific processes such as approvals before synchronizing tasks with their providers. * Support automated synchronization of configuration data between provider and consumer instances. See [Service Exchange](https://www.servicenow.com/docs/access?context=tmt-service-bridge-both-landing-page&family=xanadu&ft:locale=en-US) for more information. | | Yokohama | * Providers can now include client and UI policy scripts in remote record producers, which consumers can review and approve. * Providers can now copy local catalog items to Service Exchange as remote record producers either in bulk or individually. * Providers can simplify and streamline choice-based transform mapping with ServiceNow Now Assist. * Consumers can now add variables to remote record producers for use in consumer pre-flows. See [Service Exchange](https://www.servicenow.com/docs/access?context=tmt-service-bridge-both-landing-page&family=yokohama&ft:locale=en-US) for more information. | | Zurich | * Streamline data replication from provider to consumer instances with foundation data sync. * Enable seamless collaboration between provider and consumer with enhanced journal entry support. * Enable consumer users to access linked resources in the provider instance using magic links. See [Service Exchange](https://www.servicenow.com/docs/access?context=tmt-service-bridge-both-landing-page&family=zurich&ft:locale=en-US) for more information. | [ ]