Migration validation parameters to Azure infrastructure

oespinosa
Tera Contributor

4 hours ago

We are going to migrate our ServiceNow instance to MS Azure infrastructure.

Our Security department want to validate that the migration works fine, but we don't know what controls or which data or other validations need to do.

 

Is there any prior experience validating ServiceNow migration?

Is there any migration validation framework or scenarios to know what we need to check and validate to verify that the migration worked fine?

 

Thanks so much for any help

Regards

0 Helpfuls
  • 79 Views
1 REPLY 1

ayushraj7012933
Mega Guru

a minute ago

Hi  @oespinosa ,

You can follow a structured step-by-step validation plan after migrating your ServiceNow instance to Azure. This aligns with best practices and is typically what security and platform teams expect.

 Step-by-Step Migration Validation

Step 1: Capture Pre-Migration Baseline

Before migration, document:

  • Record counts (Incident, Task, CMDB, Users)

  • Active integrations & endpoints

  • Performance metrics (form load, API response)

 This will be your comparison reference

Step 2: Validate Instance Accessibility

  • Verify instance URL is accessible

  • Test login:

    • Local login

    • SSO (Azure AD)

Step 3: Data Integrity Check (Critical)

  • Compare:

    • Record counts (pre vs post)

  • Validate:

    • Attachments

    • Work notes / activity logs

    • Reference fields (no broken links)

Step 4: Validate Security & Access

  • Check:

    • Roles and ACLs

    • User access (internal/external)

    • SSO working correctly

 Ensure no access loss or unexpected access

Step 5: Test Integrations

  • Validate all integrations:

    • REST / SOAP APIs

    • MID Server connectivity

    • External systems (AD, monitoring tools)

 Check:

  • Credentials

  • Endpoint URLs

  • Firewall/network rules

Step 6: Validate CMDB & Discovery

  • Verify:

    • CI counts

    • Relationships (cmdb_rel_ci)

  • Run a sample Discovery to confirm working

 Step 7: Validate Jobs & Automation

  • Check:

    • Scheduled Jobs

    • Flow Designer flows

    • Business Rules

 Ensure no failures or stuck executions

Step 8: Test Notifications

  • Validate:

    • Outbound emails

    • Inbound email actions

Step 9: Performance Testing

  • Compare:

    • Form load time

    • API response time

 Identify any latency due to Azure network

 Step 10: Logs & Monitoring

  • Review:

    • System Logs

    • Node logs

 Check for errors post-migration

Step 11: Final User Validation (UAT)

  • Ask business users to:

    • Test key workflows

    • Validate end-to-end processes

0 Helpfuls