Option to 'Pull from UAT' in KM

📘

'Pull from UAT' is now 'Clone from another environment'

On 6 October 2026, KM environments became independent and Pull from UAT was replaced by Clone from another environment. You can now clone from any lower environment — not only UAT — and clone settings as well as connections and articles. Automatic back sync from Production to UAT has been switched off. For how independent environments work, see Environments in KM (Production vs UAT vs Staging).

Overview

Audience: Knowledge Management (KM) administrators

Clone from another environment copies tested connections, manually added articles and settings from a lower environment into a higher one — for example, from UAT into Production — so you don't have to re-enter configuration by hand.

Changes always move up the promotion order: Staging → UAT → Production. If your organisation also has a Pre-Prod environment, it sits between UAT and Production. You always start in the environment you are bringing changes into, then choose the lower environment to clone from. Cloning copies — the source environment keeps everything it has.

What you cloneWhere to start, in the higher environment
A connectionSettings → Integrations, on the connector
Manually added articlesHome → Add knowledge → Clone from another environment
SettingsSettings → General → Clone

What changed from 'Pull from UAT'

Pull from UAT (before 6 October 2026)Clone from another environment (now)
Source environmentUAT onlyAny environment below the one you are in
Source connection after the copyFrozen (read-only) in UAT, irreversiblyNot frozen — cloning copies, and the source environment keeps everything it has
Production → UAT back syncNew Production articles and connections were copied back to UATSwitched off for all customers. Nothing is copied between environments automatically
Connections created in ProductionA replica appeared in UATStay in Production only
Same credentials in UAT and ProductionBlocked across environmentsAllowed across environments. Credentials must be unique only within one environment
Articles you can copyPublished or In ReviewPublished only
How copied articles arriveCopied into the mapped destination folderArrive as Drafts in the destination folder and follow that environment's approval flow
Updating something you already copiedNot possible — no merge with an existing Production configurationClone again from source refreshes a cloned connection; cloning a newer article version updates the existing article
SettingsNot supportedBot settings, dashboard settings and article visibility can be cloned

Clone a connection

  1. In the higher environment, go to Settings → Integrations and select the connector. If the connector already has a connection, select + Add account.

  2. Select Clone from another environment. This option appears only when an environment below this one has a connection for that connector.

  3. Select the Source environment and the Connection to clone, then confirm.

The connection is created in this environment with the source connection's credentials, sync settings and parsing data, and a sync starts right away. Content that was already parsed in the source environment is reused where possible, which speeds up the first sync.

Not copied: the auto-sync schedule (and whether auto-sync is on), and the connection's default owner — you become the default owner. Review the result, then set up auto-sync in this environment if you need it.

A cloned connection shows a Cloned from label with the name of its source environment. To refresh it with the latest credentials and sync settings from the source, select Clone again from source. This overwrites the connection's current settings in this environment.

Keep in mind:

  • Only connections that were set up directly in the source environment can be cloned. Draft connections, and connections that were themselves cloned from another environment, are not listed — clone from the environment where the connection was originally set up.
  • You cannot clone while a sync is running on the source connection, or while a sync is running in either environment.
  • A new clone is blocked if this environment already has a connection with the same name, or a connection that uses the same credentials.

Credentials that must be unique within an environment

You can use the same credentials in different environments — for example, the same SharePoint tenant in UAT and Production. Within a single environment, a set of credentials can belong to only one connection. If you try to save a connection with credentials that another connection in the same environment already uses, the connection is not saved, and the error message names the connection that already uses them.

ConnectorCredentials that must be unique within an environment
SharePointTenant (site URL for older, non-Graph SharePoint connections)
ConfluenceSite URL
ServiceNowInstance URL
ZendeskDomain
Google DriveService account email
BoxUser ID
SFTPHost and port
WorkdayBase URL and tenant ID
SimpplrAPI hostname

Clone articles

Use this to bring manually created or uploaded articles into a higher environment. Articles that come from a connector are not listed — clone the connection instead.

  1. In the higher environment, go to Home → Add knowledge → Clone from another environment.

  2. Select the source environment and click Continue.

  3. Under Article mapping, select the articles and a destination folder. Use Add article to map more articles to other folders. You can clone up to 20 articles at a time.

  4. Click Clone.

What to expect:

  • Only published articles are listed. Articles in Draft or In Review in the source environment are not available to clone.
  • Cloned articles arrive as Drafts in the destination folder. They take the destination folder's audience and follow this environment's approval flow — review and publish them as usual. New articles are created with you as the owner.
  • Content, attachments, article settings and FAQs are copied.
  • An article you have already cloned into this environment is not listed again until a newer version is published in the source environment. Cloning that newer version updates the existing article here instead of creating a duplicate. If the article already has an unpublished draft in this environment, that draft is replaced.
  • This option is available to KM admins in UAT and Production. It is not shown in the master segment.

Clone settings

  1. In the higher environment, go to Settings → General and click Clone.

  2. Select the source environment and the settings to clone:

    • Bot settings — the settings on the Bot settings page, such as languages and knowledge search configuration
    • Dashboard settings — the settings on the Dashboard settings page, such as the approval flow and email notifications
    • Article visibility — the path-based filters described in Path-Based Access Control (Connector Filters)
  3. Click Clone and confirm.

Selected settings replace the current ones in this environment; settings you leave unchecked stay as they are. Bot settings is not offered in the master segment. The Clone button is available in UAT and Production.


Limitations

  • Cloning only moves changes up. You cannot clone from Production into UAT or Staging. To get Production content into a lower environment, set up the same connection there and run a sync. KM settings and manually added articles have to be updated in the lower environment by hand.
  • Auto-sync schedules and default owners are not cloned. Set up auto-sync in the target environment after cloning, if you need it.
  • Connector-synced articles cannot be cloned as articles. Clone the connection instead.
  • Staging has no environment below it, so Clone from another environment is not shown there.
  • Sync history is not copied. A cloned connection starts with its own sync log history in the target environment.

Best practices

  • Finish testing before you clone: validate content, permissions and bot responses in the lower environment first, then clone the change up.
  • Clone instead of re-creating: cloning carries over credentials, sync settings and parsing data, so you don't have to re-enter configuration by hand.
  • Check auto-sync in every environment: schedules are never cloned. If more than one environment auto-syncs the same source, your source system receives requests from each of them — keep auto-sync off in lower environments unless you need it, or stagger the schedules.
  • Review sync logs after cloning: use KM Sync Logs to confirm the first sync in the target environment completed as expected.

Frequently asked questions

Q: Where did the "Pull from UAT" button go?
A: It has been replaced by Clone from another environment — under Home → Add knowledge for articles, and on the connector under Settings → Integrations for connections.

Q: Why don't I see "Clone from another environment"?
A: Staging has no environment below it, so the option is not shown there. For connections, the option appears only when a lower environment has a connection for that connector that was set up directly in that environment. For articles, the option is available to KM admins in UAT and Production, outside the master segment.

Q: Does cloning move content out of the source environment?
A: No. Cloning copies. The source environment keeps its connections, articles and settings.

Q: Can I use the same SharePoint tenant or ServiceNow instance in UAT and Production?
A: Yes. The same credentials can be used in different environments. Within one environment, each set of credentials can be used by only one connection.


Did this page help you?