Skip to content

Export guide

How to export your Azure DevOps data

Last verified: 2026-10-09 · Menu names change between plans and versions; check the vendor documentation below, and we confirm exact steps with you once you qualify.

Short answer

Azure DevOps (code hosting and work tracking) holds work items, pull requests, reviews and pipelines. You run the export yourself, from the app or through its API, after removing personal and confidential details. Nothing leaves your company until you approve it.

Export from the app

  1. Step 1

    Check licenses and ownership

    You need Project Administrator permissions or higher. Verify your organization has the 'Boards' service enabled.

  2. Step 2

    Create a work item query

    Go to Boards → Queries, create a 'New query' that returns all work items, and ensure all columns you need are added to the view.

  3. Step 3

    Export to CSV

    Select the 'Actions' (three dots) icon in the query results view and choose 'Export to CSV' to download the file.

  4. Step 4

    Check the file before sharing

    Open a sample of the export, confirm the date range and record count, and flag anything personal or confidential. Don't send anything yet — we review the package together first.

Export through the API

  1. Step 1

    Create a read-only key

    In User settings → Personal access tokens, create an API token or app with read-only scopes. Keep it inside your company; never send it to SourceX.

  2. Step 2

    Query OData Analytics

    Access the OData endpoint at https://analytics.dev.azure.com/{org}/{project}/_odata/v3.0-preview/WorkItems to fetch historical work item data.

  3. Step 3

    Pull history in batches

    Page through records by date range, respecting rate limits. Save raw JSON to your own storage. Large histories can take several days.

Plan limits and formats#

  • Limits and formats depend on your plan and are confirmed with you after qualification.

What to leave out#

  • Names, emails, phone numbers and addresses of customers and staff
  • Passwords, API keys, tokens and other credentials
  • Payment card and bank details
  • Attachments you haven't reviewed (they often hold IDs or contracts)
  • Records covered by client NDAs, privilege or contracts that limit reuse
  • Anything you mark confidential, such as pricing or strategy

Terms to check first#

  • Your content is usually yours, but plan terms can limit bulk export, API use or automated access.
  • Check whether your plan includes the export or API features you need before starting.
  • Respect API rate limits; large exports may need to run in batches over several days.
  • Don't share admin logins. You run the export yourself, with our guidance.

Vendor documentation

What happens after the export

See what your Azure DevOps records are worth to AI buyers and how licensing works, step by step.

Read the Azure DevOps licensing guide

Related

Read why buyers want this data

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies Talk to SourceX
See if your company qualifies