- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-16-2022 01:20 AM
We have a requirement to migrate knowledge articles from a third-party tool to ServiceNow.
The third-party tool can export articles only in PDF or HTML format.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-16-2022 01:27 AM
Hello
Please check Lauren's answer in below thread.
Please mark my answer as correct based on Impact.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-16-2022 03:12 AM
Hello, Nawazish! You're going to get a cleaner outcome with your articles if you use HTML.
In our experience - bringing in articles one at a time so we could control the HTML has led long-term to cleaner articles with more consistent formatting that are easier to edit in the long-run.
When you import from PDF or Word, there's a lot of extraneous HTML code (i.e., instead of plain paragraph tags <p>, you end up with style=format this and size that and so many margins!!! - it's a mess). When you go back in to edit later, it's hard to make a simple edit from the Content field in the knowledge form/template without messing up the coding. Your edit will (for whatever reason) not take on the code of the previous article, etc. Then, we find we have to spend time looking up the style, the formatting, etc., and fixing it in the source code.
Since most of the people working on the articles aren't well versed in HTML coding, they're more likely to make it worse or not be able to find it at all.
Take a look at my response that Saurav11 linked to, and please reply if you have follow-up questions. Happy to help. Thanks!