--- title: "How to Migrate Confluence to a ServiceNow Knowledge Base" description: "The four ways to move Confluence pages into ServiceNow Knowledge Management, from HTML export and the REST API to Store apps and an agentic migration, with what each does to page trees, macros, attachments, and links." canonical: https://ocho.bot/blog/confluence-to-servicenow-knowledge-base-migration last_updated: 2026-09-12 --- # How to Migrate Confluence to a ServiceNow Knowledge Base > The four ways to move Confluence pages into ServiceNow Knowledge Management, from HTML export and the REST API to Store apps and an agentic migration, with what each does to page trees, macros, attachments, and links. Published: 2026-09-12 There is no one-click path from Confluence to ServiceNow Knowledge Management. ServiceNow's official Confluence Cloud spoke can list spaces and pages but has no action that returns a page's body, so it cannot move content on its own. What works is one of four routes: export the space to HTML and load it, pull page bodies from the Confluence REST API and load them through ServiceNow's Table API, buy a ServiceNow Store app that does the pull for you, or run an agentic migration that reads the pages and drafts articles. This guide walks through each and the four things that break in every one: page trees, macros, attachments, and links. ## First, what Confluence content looks like to ServiceNow A Confluence page is stored in "storage format," an XHTML dialect with Confluence-specific elements for macros, layouts, and links to other pages. A ServiceNow knowledge article is plain HTML in the `text` field of `kb_knowledge`, limited to what the TinyMCE editor supports. The conversion has to: - Flatten the page tree. Confluence spaces nest pages many levels deep. ServiceNow organizes articles by knowledge base and category, and most instances use one or two category levels. The tree becomes a category assignment plus, where it matters, a "see also" list. - Resolve macros. Info panels, expand blocks, code blocks, tables of contents, Jira issue macros, and page includes have no HTML equivalent until something renders them. The export views render some; the storage format leaves them as markup. - Move attachments and images. Confluence stores them per page; ServiceNow stores them per article record, and inline images need new URLs. - Rewrite links. Every link to another Confluence page must point at the corresponding ServiceNow article, which means the target article must exist first. ## Route 1: Export the space to HTML, then load it Confluence Cloud (Space settings, General, Export space) and Data Center (Space tools, Content Tools, Export) both export a space as HTML. The export is a zip of one HTML file per page plus the attachments, organized in folders by page id. It excludes blog posts and comments, and it requires space administrator rights on Cloud or the Export Space permission on Data Center. 1. Export each space to HTML. 2. Write a script that walks the zip, reads each page's HTML, strips Confluence's wrapper markup and navigation, and rewrites image `src` attributes to placeholders. 3. Create each article in ServiceNow through the Table API, upload the page's attachments with the Attachment API, and replace the placeholders with the attachment URLs. 4. Run a second pass that rewrites page-to-page links to the new article numbers, using the page id to sys_id map from step 3. 5. Review in Draft, then publish through the knowledge base workflow. Steps 3 and 4 are described with examples in [How to bulk import knowledge articles into ServiceNow](/blog/bulk-import-knowledge-articles-into-servicenow). The export route has one advantage: macros are rendered to HTML in the export view, so info panels and code blocks arrive as styled blocks rather than raw markup. It has one disadvantage: it is a snapshot, so anything edited in Confluence after the export is lost unless you export again. ## Route 2: Confluence REST API to ServiceNow Table API For a live pull, or when you want to pick pages rather than whole spaces, use the Confluence REST API. - REST v1: `GET /wiki/rest/api/content/{id}?expand=body.storage` returns the storage-format body. Use `expand=body.view` for rendered HTML instead. - REST v2: `GET /wiki/api/v2/pages/{id}?body-format=storage` or `body-format=export_view` for rendered HTML, with the `read:page:confluence` scope. The `export_view` body is closest to what a browser shows and the easiest to convert. From there the load is the same as route 1: create the article with the Table API, upload attachments, rewrite links in a second pass. On Data Center, an XML export API exists from Confluence 8.3, but there is no REST endpoint that produces the HTML or PDF space export, so the page-by-page pull is the only scripted route. The REST route is the one to choose when the migration will run more than once, for example a pilot on one space followed by the rest, or a nightly sync during a transition period. ## Route 3: ServiceNow Store apps Several vendors sell the scripting in routes 1 and 2 as an installable app. - **Ams1 Confluence Articles to KB** (ServiceNow Store) migrates Confluence Cloud spaces and pages into knowledge articles, including attachments and images, according to its listing. - **AMSONE OnPremise Confluence pages to KB** (ServiceNow Store) does the same for hosted and on-premises Confluence. - **SyncsNow**, from the same vendor, adds ongoing synchronization between Confluence pages and ServiceNow articles. - **Precision Bridge Data Migrator** (ServiceNow Store) is a general migration tool between service management platforms; the vendor also publishes a Confluence-to-ServiceNow template. We have not run these apps ourselves, so treat the descriptions as vendor claims. The questions to ask a vendor are the four from the top of this guide: how do they map the page tree, which macros survive, how are attachments re-linked, and what happens to page-to-page links. Also ask what the app does with the twenty percent of pages that are drafts, duplicates, or abandoned, because the answer is usually "migrates them." ## Route 4: Agentic migration with Ocho Routes 1 through 3 move pages. The community threads on this migration agree on the harder problem: a Confluence space accumulated over years contains pages that contradict each other, pages nobody has opened since 2019, and five versions of the same runbook in different team spaces. Moving them all produces a ServiceNow knowledge base with the same faults and a new URL. Ocho connects to Confluence directly and reads every page before anything is created. AI agents build a knowledge graph of the spaces: which pages cover the same topic, which version is newest, which are dead. Each page gets a verdict, keep, archive, or duplicate, with a logged reason. Duplicates collapse into one drafted ServiceNow article that cites its source pages. Your experts approve each draft, and Ocho publishes only the approved ones to ServiceNow. After cutover, new content is triaged the same way. This is a managed engagement run by a forward deployed engineer, not a Store app. It starts with a two-week, fixed-price triage of up to 10,000 pages, and the triage report, with every verdict and reason, is yours to keep. It fits a Confluence estate large enough that nobody can read it; a single well-kept space of a hundred pages is better served by route 1. The engagement is described on the [migration page](/leave-sharepoint), which lists Confluence among its sources. ## Which route - **One space, well maintained, one-time move:** route 1. - **Several spaces, staged rollout, or a sync period:** route 2. - **No scripting capacity, budget for a license:** route 3, after asking the four questions. - **Thousands of pages with duplication and no owners:** route 4. ## Questions ### Does the official Confluence Cloud spoke migrate pages? No. Its nine actions cover looking up spaces, pages, groups, and users, searching content, and reporting personal data. None returns page body content. It needs an IntegrationHub subscription. ### What happens to Confluence comments and page history? The HTML export excludes comments. Page history is not exported by any route. If a page's edit history matters for audit, keep the Confluence space read-only rather than deleting it. ### Can Now Assist draft the articles from Confluence pages? Not as a documented feature. Now Assist for Knowledge Management generates articles from resolved incidents and cases. ### How long does a Confluence to ServiceNow migration take? The export and load of a space is hours to days. Reviewing and deduplicating the content is weeks to months for a large estate, which is why the content review, not the tooling, decides the timeline. ## Sources and how we checked Checked on 2026-09-12 against Atlassian and ServiceNow documentation, the ServiceNow Store, and community threads. - Atlassian: [Export content to Word, PDF, HTML and XML (Cloud)](https://support.atlassian.com/confluence-cloud/docs/export-content-to-word-pdf-html-and-xml/), [Data Center export](https://confluence.atlassian.com/doc/export-content-to-word-pdf-html-and-xml-139475.html) - Atlassian: [Confluence REST API examples](https://developer.atlassian.com/cloud/confluence/rest-api-examples/), [REST API v2 pages](https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-page/) - ServiceNow docs: [Confluence Cloud spoke](https://www.servicenow.com/docs/bundle/yokohama-integrate-applications/page/administer/integrationhub-store-spokes/concept/confluence-cloud-spoke.html), [Table API](https://www.servicenow.com/docs/r/api-reference/rest-apis/c_TableAPI.html), [Attachment API](https://www.servicenow.com/docs/r/api-reference/rest-apis/c_AttachmentAPI.html) - ServiceNow Store: [Ams1 Confluence Articles to KB](https://store.servicenow.com/store/app/80d9eb621b246a50a85b16db234bcbd8), [AMSONE OnPremise Confluence pages to KB](https://store.servicenow.com/store/app/c5ab6faa1b246a50a85b16db234bcb45), [Precision Bridge Data Migrator](https://store.servicenow.com/store/app/adfda7e61b646a50a85b16db234bcb35) - ServiceNow community: [Transfer Confluence to ServiceNow KB](https://www.servicenow.com/community/knowledge-managers/transfer-confluence-to-servicenow-kb/td-p/352469) --- Ocho — AI knowledge orchestration · [Home](https://ocho.bot/) · [Docs](https://ocho.bot/docs) · [Blog](https://ocho.bot/blog) · [About](https://ocho.bot/about) · [Developers](https://ocho.bot/developers) · [Contact](https://ocho.bot/contact) · [llms.txt](https://ocho.bot/llms.txt)