Skip to main content

Every ServiceNow customer arrives at the same realization eventually: that “small custom thing” they greenlit two years ago is now blocking the family upgrade. Multiplied across ten such decisions over five years, the platform team has gone from feature delivery to maintenance gridlock.

The compounding interest of customization

Customizations aren’t inherently bad. The problem is that each one adds three ongoing costs that nobody priced at the time of approval:

  1. Upgrade testing time. Every custom artifact needs regression coverage on every family upgrade. The cost scales linearly with customization count.
  2. Out-of-the-box feature drift. When ServiceNow ships a new feature in the same area as your customization, you have to choose: keep yours, adopt theirs, or merge them. Each choice costs analysis time.
  3. Integration brittleness. Custom tables and fields break when integrating with new tools — vendors expect standard data models.

A practical audit approach

For Mergen platform-health audits, we use a 4-quadrant model:

Most platforms we audit have 20-30% of customizations in the bottom-right quadrant. Removing them typically returns 6-10 weeks of upgrade-testing time per release, plus eliminates a class of regression failures.

How to actually decommission

Start with usage data. ServiceNow exposes table-level access patterns — if a custom table hasn’t been written to in 90 days, it’s a candidate. If a custom UI policy hasn’t fired in 6 months, the rule it depends on probably isn’t needed. Build a list, route each candidate through a 30-day “if no one screams, we delete” process, and chip away.

Planning Your Next Initiative?

Whether you're modernizing an existing platform, implementing new capabilities, or exploring AI-driven transformation, Mergen's certified experts will help define the right roadmap, scope, and delivery approach for your business.

Book a Discovery Call