Published November 19, 2026
What the job involves
A ServiceNow implementation puts a set of service processes onto one platform. This note covers IT Service Management (ITSM). ServiceNow describes ITSM as a suite of applications for the end-to-end delivery of IT services. The suite includes Incident Management, Problem Management, Change Management, Request Management and Service Level Management, among others, sold in different subscription packages.
ServiceNow names each release family. Australia followed Zurich and became generally available on May 5, 2026. Brazil reached early availability on September 24, 2026, and ServiceNow lists its general availability as Q4 2026.
What goes in the first release
Start with a few processes on clean data. Replicating every workflow from the old tool adds customization and delays the release.
Incident, request and knowledge are candidates for a first release because the service desk uses them daily. Change management relies on the CMDB. A change request lists the affected CIs, and Refresh Impacted Services fills in the services related to them. Consider adding change management once the CMDB holds those CIs and services.
Configure, customize or build
Each requirement lands in one of four places.
| Approach | What it means | What happens at upgrade |
|---|---|---|
| Use as delivered | Adopt the baseline process and forms, and change the way of working instead. | No skipped records. Test as usual. |
| Configure | Change behavior with the platform's built-in tools, without changing baseline flows or code. | Baseline records are untouched and update normally. |
| Customize | Change flows or code that are part of the baseline installation. | The upgrade skips customized records. Each one must be reviewed and retained, reverted or merged, then tested. |
| Build separately | Create a new application or table for a need the product does not cover. | Your own code. You maintain and test it. |
ServiceNow states that Customer Service and Support will not support problems caused by custom code, and may recommend reverting to the baseline. Customizations create records in the Customer Update table (sys_update_xml). That table also holds configuration changes, so keep a separate count of customizations from the first sprint.
The order of the work
- Name the process owners and the platform owner. One person per process decides requirements. One person owns the instance and its upgrade calendar.
- Agree the processes before configuring them. Write down states, assignment rules, approvals and service levels for each process. Record each departure from the baseline process, with the reason.
- Load the foundation data. ServiceNow's Common Service Data Model (CSDM) treats foundation data as a prerequisite: it must exist before you can use ServiceNow products or add data to the CMDB. CSDM lists company, business unit, department, location, group and user as common foundation data. Decide the source system and owner for each.
- Set up the instances and the release path. Configuration moves from development to test to production. Decide how changes are packaged, reviewed and promoted, and who approves a move to production.
- Build the CMDB in stages. CSDM sets out stages called Foundation, Crawl, Walk, Run and Fly. Crawl covers the base CMDB tables used by ITSM. Walk adds network infrastructure and the applications technical teams support. Run links technology to the business that uses it.
- Build integrations and migrate data. Connect identity, monitoring, asset and HR sources. Move open records and the history people need.
- Test, including regression tests you can rerun. The Automated Test Framework (ATF) creates and runs automated tests to confirm the instance works after a change. Build tests during the project for use at the first upgrade.
- Go live and plan the first upgrade. Schedule the next release family before go-live, with testing owners.
Where the effort goes
- Process agreement. Each team has its own assignment rules, categories and priorities. Plan time to agree one version before anyone configures it.
- The CMDB. ServiceNow's CMDB Health measures completeness (required and recommended fields left empty), correctness (including duplicate, orphan and stale CIs), compliance against defined certificates, and relationships. Assign an owner to fix what it reports, in the CMDB or in the source system.
- Reconciling data sources. The Identification and Reconciliation Engine (IRE) uses identification rules to prevent duplicate CIs, and reconciliation rules so that only authoritative data sources write to the CMDB. Someone has to decide which source is authoritative for which CI class and attribute.
- Integrations behind the firewall. The MID Server is a Java application that runs as a Windows service or UNIX daemon on a server in your network, and moves data between the instance and external applications. It needs a server, network access and an owner.
The detail plans leave out
- Update sets carry configuration, not data. ServiceNow documents that update sets do not capture task or process data, and do not track removal of tables. For larger data transfers it recommends an import set or web service.
- Import sets need a matching key. An import set table stages incoming records, a transform map defines how fields map to the target table, and coalesce updates existing records instead of creating new ones. Without a coalesce field, every row is inserted as a new record.
- Cloning overwrites development work. A clone copies data and metadata from one instance to another, and in-progress development work on the target is overwritten. ServiceNow's clone documentation says to export in-progress update sets before a clone and reimport them afterward.
- ATF does not run in production by default. The property that runs tests is off by default to prevent running them on production by accident. Tests belong on development and test instances.
- Domain separation is permanent. It partitions data, processes and administration inside one instance and is designed primarily for service providers. ServiceNow states it adds administration overhead and, although it can be disabled, it cannot be removed from an instance.
- Service Graph Connectors come from the ServiceNow Store. They are predefined integrations that import and standardize third-party data in the CMDB, use IRE to identify it, and map it to the locations CSDM specifies. Check for one before building a custom integration.
The subscription and the cost
Subscription Management measures and audits per-user subscriptions by roles. Roles that need a subscription are called measured roles, and you allocate a subscription by adding groups that hold those roles to a product subscription.
- Per-user subscriptions use meters such as Fulfiller Users and Business Stakeholder Users, based on roles and access rights.
- Unrestricted User subscriptions count every active user on the instance, whatever their roles.
- Capacity subscriptions track measured units such as transactions, records created or resources managed.
- Over-allocation means more users hold an entitlement than you bought. ServiceNow says to resolve it by removing users or groups from the subscription or buying more.
Role design is a cost decision. Giving a broad group a fulfiller-type role can change the subscription count. Agree the role model with the contract owner before go-live.
Skills and operations
After go-live, plan for a standing platform team: an owner, administrators, developers and someone responsible for the CMDB. If a partner builds the first release, decide who handles upgrades, skipped records and new requests afterward.
Upgrade Center plans and manages upgrades, and the Upgrade Preview module lets you explore the release versions available to you. ServiceNow advises upgrading the instances furthest from production first and testing after each one. Instance Scan checks an instance for configurations that indicate health issues and is meant for release management and for use before and after upgrades.
Settle these first
- Which processes are in the first release, and who owns each one?
- Who decides whether a requirement is met by configuration or needs customization, and is the count reported?
- Which system is the source for users, groups, locations and companies?
- Which source is authoritative for each CI class and attribute in the CMDB?
- Which roles are measured in your subscription, and who approves new role assignments?
- Do you need domain separation, given that it cannot be removed?
- Who will run the first upgrade, and when?
Questions
- What is the difference between configuring and customizing ServiceNow?
- Configuration changes behavior with built-in tools and leaves baseline flows and code untouched. Customization changes baseline flows or code. Customized records are skipped at upgrade and must be processed by hand. ServiceNow's Customer Service and Support will not support problems caused by custom code.
- Do we need a full CMDB before going live with ITSM?
- No. CSDM sets out stages, and the Crawl stage covers the base CMDB tables used by ITSM. Foundation data must be in place first. Change management draws on the CMDB to list the services a change affects, so it depends more on CMDB quality.
- Can update sets move our data from the old tool?
- No. Update sets capture configuration, not task or process data. ServiceNow recommends import sets or web services for larger data transfers.
- What happens to our customizations when we upgrade?
- The upgrade skips customized records and logs each one. An administrator reviews each skipped record and retains it, merges in the new baseline changes, or reverts to the baseline, then tests the result.