Data migration: Transferring work items (like AMS tickets) from Azure DevOps to ServiceNow.

Process based on established methods and tools commonly used for transferring work items (like AMS tickets) from Azure DevOps to ServiceNow. This includes handling historical data such as the last 6 months. Many organizations achieve this through APIs, built-in integrations, or third-party tools to ensure data fidelity. If you're looking for someone with hands-on experience, I recommend checking ServiceNow's community forums

servicenow.com +2

 or LinkedIn groups focused on DevOps and ITSM migrations, where users often share case studies. Tools like OpsHub, Exalate, or ZigiOps also have support teams that can guide you through custom setups

marketplace.visualstudio.com +2

.Steps for MigrationThe process typically involves exporting data from Azure DevOps, mapping it to ServiceNow's structure (e.g., incidents, change requests, or custom tables), and importing it. You can use ServiceNow's native Azure DevOps integration for ongoing sync, but for a one-time historical transfer, third-party tools or scripts are often more efficient. Here's a high-level step-by-step guide:Prepare and Assess Data: Identify the scope: Filter Azure DevOps work items (e.g., bugs, tasks, user stories) for the last 6 months using queries in Azure DevOps (e.g., via WIQL or the Boards query editor). Include fields like title, description, status, attachments, comments, history, assignments, and custom fields.

Export a sample dataset (e.g., via CSV export from Azure DevOps or REST API calls) to review for completeness.

In ServiceNow, set up corresponding tables (e.g., incident or task tables) and ensure you have admin access. Install any relevant plugins like "Microsoft Azure DevOps Pipeline" or "Agile Development 2.0" if not already active

servicenow.com +1

.

Choose an Integration Method:Native ServiceNow Tools: Use ServiceNow's DevOps Change Velocity or Agile Development integration to onboard Azure DevOps data. Create an Azure DevOps tool record in ServiceNow, configure OAuth or PAT (Personal Access Token) authentication, and trigger imports for projects, teams, iterations, and work items

servicenow.com +1

. This maps Azure Boards work items to ServiceNow states and types automatically.

Third-Party Tools: For more control over historical data, use tools like:OpsHub or Getint: Configure systems, select projects/entities (e.g., work items to incidents), set sync direction (one-way migration), apply filters (e.g., date range for 6 months), and map fields

marketplace.visualstudio.com +1

.

Exalate or Unito: Install apps on both sides, create a connection, choose flow direction (e.g., Azure DevOps → ServiceNow), set rules (e.g., filter by creation date), and map fields bidirectionally if needed for testing

exalate.com +1

.

ZigiOps: Set up bi-directional sync for work items to incidents, with support for attachments and history

docs.zigiwave.com +1

.

Custom Scripting: If budget is tight, use Azure DevOps REST APIs to export data (e.g., GET work items) and ServiceNow's REST APIs or Flow Designer to import via JSON payloads

servicenow.com +1

. Tools like PowerShell or Python can automate this.

Map and Transform Data:Align fields: E.g., Azure DevOps "State" to ServiceNow "State," "Description" to "Description," and handle custom fields manually.

Transform data: Convert formats (e.g., dates, priorities) and preserve history (revisions, comments) by importing as journal entries in ServiceNow.

Test mappings on a small subset to ensure no data corruption.

Execute the Migration:Run the export/import in batches (e.g., by date or priority) to avoid overwhelming systems.

Use filters like "Created Date >= 6 months ago" in queries.

Monitor progress via tool dashboards or logs.

Validate and Go Live:Verify imported data in ServiceNow for accuracy (e.g., spot-check tickets, attachments, and audit logs).

Set up ongoing sync if needed (e.g., for future tickets).

Train users on the new ServiceNow workflow and archive Azure DevOps access.

This process can take from a few days to weeks, depending on data volume and complexity. Aim for a non-production environment first.Possible IssuesMigrations like this aren't always straightforward, and issues can arise due to platform differences. Here are common ones based on reported experiences:Data Loss or Incompleteness: Attachments, inline images, rich text formatting, or full revision history might not transfer perfectly, especially with custom fields or large volumes. Solution: Use tools that support rich data sync (e.g., OpsHub) and validate exports

opshub.com +1

.

Field Mapping Mismatches: Azure DevOps process templates (e.g., Agile vs. Scrum) differ from ServiceNow's ITSM structures, leading to mismatched workflows or states. Custom fields may require manual scripting

opshub.com +1

.

Authentication and Connection Problems: Tokens expire, or connections break after ServiceNow updates/patches. OAuth setup can be tricky

servicenow.com +1

.

Sync Delays or Loops: Real-time sync might lag, or bidirectional setups cause infinite updates (e.g., comments bouncing back). One-way migration helps avoid this

servicenow.com +1

.

Performance and Scalability: High-volume data (thousands of tickets) can slow down imports or hit API rate limits. Batch processing mitigates this

zigiwave.com

.

Custom Integration Maintenance: If using scripts, changes in APIs or schemas can break things long-term. Prefer no-code tools for sustainability

zigiwave.com +1

.

Compliance and Security: Ensure data transfer complies with your policies (e.g., no data replication in third-party tools). Test for errors like failed inbound events

servicenow.com +1

.

To minimize risks, start with a proof-of-concept on a subset of data and involve your IT teams early. If this is complex, consider consulting a partner specializing in ServiceNow integrations.Let me know if you need more details on any step!