How to import a large number of formatted Word documents into ServiceNow Knowledge Articles
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
We have a large number of Word documents that have tables, bullet points, numbered outlines, table of contents, etc. Is there a way to import those documents as Knowledge Articles without losing the formatting, particularly tables?
We attempted to import files, but the formatting was really off. We would prefer to have minimal clean-up. It looks like this has been an issue for a while. Are there any new changes that will make this process available/easier? Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
There is an external plugin called ImportMate that can meet your requirement exactly.
For more details, you can reach out to below profile.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @NitaW , and thanks @Raghu Ram Y for the mention.
Full disclosure: I'm co-founder of SwissFlowIt, the company behind Importmate.
Going through your list:
- Large number of documents: yes. You drop hundreds of files at once and each one becomes a draft article in the knowledge base and category you pick, with its images.
- Tables: the structure is kept, including merged cells. Colors and borders are not, same as with the OOB import, but one CSS rule in your portal theme gives every table a consistent style. Keeping the original colors and borders is on our roadmap.
- Bullet points: kept.
- Numbered outlines: kept.
- Table of contents: kept, with links to each section.
On top of Word, it also imports PDF (scanned ones included), PowerPoint and Excel, which the OOB import
doesn't.
Happy to run two or three of your hardest documents so you can judge the result.
Store listing:
https://store.servicenow.com/store/app/a8277a92937cc3d41caaf76e1dba100f
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi @NitaW ,
As far as I can see nothing has changed on the OOB side. Word import (Knowledge > Articles > Import Articles) behaves the same in the current docs, and most of what you’re seeing is documented behaviour. It’s quicker to work around each issue once than to fix articles one by one.
Tables are the main issue. The importer keeps the table structure but drops table styling and borders by design, which is why everything looks off. You can fix that once in the portal instead of per article. On kb_article_view, Ctrl+right-click the article, open Instance Options on the Knowledge Article Content widget, and add this to the CSS field. Switch to the Knowledge Management Service Portal scope first.
/* imported Word tables come in without borders */
table { border-collapse: collapse; }
th, td { border: 1px solid #ccc; padding: 4px 8px; vertical-align: top; }
This only fixes the portal. Classic UI and Workspace will still show plain tables.
Numbered outlines: normal numbered and bulleted lists import fine, though bullets become dots. Numbers on headings are dropped. If you need them, convert them to text in Word before importing: Alt+F11, open the Immediate window, run ActiveDocument.ConvertNumbersToText, then save. That flattens every list in the document to plain text, so only use it where section numbers matter, and test it on a copy first.
Table of contents: the importer doesn’t preserve it, so delete it before importing. Use the TOC button in the article editor instead. It builds a linked TOC from Heading 1 to 3, and if the button is missing you can add it through the TinyMCE attributes.
Before you import, a few more things help:
- Use Word’s built-in heading styles.
- Save .doc files as .docx, because links only survive in .docx.
- Keep file extensions lowercase.
- Import in batches. Closing the tab cancels any uploads still in progress.
Images get embedded automatically, so you don’t need to re-add them.
If that still leaves too much cleanup, your options are Importmate (mentioned above) or your own pipeline: convert to HTML with Pandoc or Mammoth, load kb_knowledge through an import set or the Table API, and push images through the Attachment API. Importmate’s Store listing says documents are converted on the vendor’s cloud service, so get security sign-off before sending anything. Neither option keeps table borders, so you’ll want the CSS change either way.