Knowledge Management
Love the Template, Dread the Rebuild: How Do You Move Old Knowledge Articles Into a Modern Design?
Your team just approved a new article template. Clean header, clear sections, a layout that finally works on a phone. Then someone asks the question every onboarding eventually reaches: "Love the template. Now how do I get my content into it without rebuilding the whole article?" Multiply that by a few hundred articles, and that's the real project. Here's how it actually goes.
Why Does Moving to a Modern Design Stall?
Because the design is the easy part. The content is where the hours go.
These are the pain points we see in almost every onboarding:
The rebuild math: Copy, paste, reformat, check. One article is an afternoon of fiddling. A few hundred is a quarter of someone's year.
Fear of touching approved wording: HR and policy content was reviewed for a reason. Nobody wants a refresh to quietly rewrite it.
No two starting points alike: Pasted Word docs, old HTML, inline styles, and tables that only work on a desktop, all in the same library.
The developer queue: When the design needs something the authoring tools can't do, someone files a ticket for custom CSS. Then does it again for the next ten articles.
Reviewers buried at the end: If everything gets rebuilt at once, approvers face a mountain of articles on the same week.
The half-finished library: Projects stall midway, and two looks side by side is worse than one old one.
None of these are about effort or motivation. The work grows with every article, not with every decision, so the bigger your library, the less likely a manual refresh ever finishes. It also lands on the people with the least spare time: the knowledge manager who owns the project, and the subject matter experts pulled in to check articles they wrote years ago.
If your library is a few dozen articles, a focused week by hand may be all it takes. Past that, the math stops working.
So How Do You Get Existing Content Into the New Template?
Let AI do the fitting, and keep a person on the approval.
ServiceNow is strong on new content. Now Assist can draft articles from resolved cases and incidents (ServiceNow docs), and the Knowledge Center article editor adds block-based editing that works with the templates you already have (ServiceNow docs). Amaze focuses on the content you already have, moving it into the design your team approved.
One article at a time. Open the article in the Amaze builder, hover over your approved template, and click Enhance. AI fits the existing content into the template right on the canvas, where you keep editing as normal. Nothing publishes until you say so.
A whole library at once. From the knowledge list, select the articles, choose AI Template Migration, pick one template, and queue the batch. You can name it, notify the right people, and add your own instructions for the AI. The batch runs as a record you can follow, from waiting to running to completed, and if something fails, the record tells you why. Need to stop partway? Cancel it, and the articles still in the queue won't start.
When the batch finishes, each migrated article gets a preview and an Approve button. Only approved articles come back as new drafts in your knowledge base, ready for your normal publishing workflow. Your published articles stay exactly as they were until then.
Which one when? Enhance suits the articles you're already editing, and the high-visibility ones you want to watch closely. Bulk suits groups that share a shape, like all your IT how-tos or all your HR policies, since each batch uses one template. Most teams use both: Enhance to prove the template works, then bulk for the rest of the group.
Both run on the AI your organization already approved, including Now Assist, under your own credentials, which we never ask to see. You do need that connection in place first. Review is real work that grows with template complexity, so a template with tabs and dropdowns takes longer to check than a simple one. And the AI keeps your content, so an outdated fact stays outdated until its owner fixes it.
What Changes Once Your Articles Look Modern?
Three things, and they compound.
Articles get read. Clear headings, navigation and a layout that works on a phone make the answer easier to find than a wall of text. An employee who finds the answer in the article doesn't need to open a ticket to ask for it. ServiceNow itself makes the point that AI depends on accurate, fresh, well-structured content (ServiceNow Community), so structure helps people and AI alike.
Modern doesn't have to mean difficult. A Word paste, old HTML and plain text all take the same route into the same template. One article is a click, and a library is a batch. Authors stop needing a developer to make a page look right, because the template already does.
One look across the organization. HR, IT and Finance articles finally feel like they came from the same company, while each team can keep its own templates. Amaze styling stays with the article, so you can redesign the portal without worrying about your content. And when the brand changes again, the same tool rolls the new design through, and runs an audit when your writing standards change.
If most employees get answers from a virtual agent and never open articles, visual polish matters less for you. Structure still pays off either way.
Where Should You Start?
With the articles people actually open.
Pick your most-viewed articles whose content is settled, enhance one, and check it carefully. If it holds up, batch the rest of that group into the same template. Assign each batch's review to the people who own that content, so approvals come from someone who knows whether the facts are still right. Leave anything mid-revision for later, because migrating content that's about to change means reviewing it twice.
Here's a ten-minute version. Open your five most-viewed articles on your phone. For each one, note its starting point (Word paste, old HTML, plain text) and whether a reader could find the answer in thirty seconds. That list is your first batch.
Frequently Asked Questions
Does migration change the wording of my articles?
It's built to keep your content and fit it into the template. Nothing is final until someone reviews and approves it.
Do we need Now Assist?
No. Amaze works with Now Assist or another LLM your organization has approved, under your own credentials.
What happens to published articles during a bulk migration?
They stay exactly as they are. Approved results come back as new drafts that you publish through your normal workflow.
Can different articles go to different templates?
Yes, with one template per batch. Group similar articles and run a batch for each template.
Can we stop a batch once it starts?
Yes. Cancelling stops the articles still in the queue, while any already in progress finish.
Will Amaze styling affect our portal?
No. It stays with the article, so portal changes and article changes don't collide.
What if our brand changes again next year?
New articles follow the updated template right away. Existing ones roll through in another reviewed batch.