MANUAL RE-ENTRY
Copy-paste is not a process.
Turning a 40-page SRS into work items by hand takes days and introduces errors on every field, every time it's re-typed.
Add Your Heading Text Here
SMART IMPORT Word & PDF to Azure DevOps work items
Turn Existing Documents Into Structured Work Items, Automatically.
Smart Import provides a guided workspace for converting Microsoft Word and PDF documents into fully structured Azure DevOps work items — all within a single, end-to-end wizard that runs from Upload through Parse, Map & Classify, Link, Preview, and Import.
100% native to Azure DevOps · .docx & .pdf supported · Zero manual re-entry
Smart Import — Map & Classify
Step 3 of 6 · auto-generated outline
Upload
Parse
Map & Classify
Link
Preview
Import
1. Introduction
Heading → Epic
Work itemMapped
2. Functional Requirements
Heading → Feature
Table rows → 12 Stories
48 headings mappedto Azure DevOps work items
Imports directly from the documents you already have
Microsoft Word (.docx)
PDF (.pdf)
Azure DevOps
Smart Doc
THE PROBLEM
Specs live in Word. Work lives in ADO. Someone has to bridge the gap.
Every legacy requirements document becomes hours of copy-paste, and every copy-paste is a chance to get it wrong.
LOST STRUCTURE
Headings become guesswork.
Paste a Word document into ADO and the outline, the hierarchy, and the intent behind each section disappear along with it.
NO TRACEABILITY
Where did this work item come from?
Without a link back to the source document, nobody can prove which paragraph a requirement came from — or that anything was missed.
HOW IT WORKS
From source document to work items in six guided steps.
Smart Import runs a single wizard from raw file to committed work items — no scripts, no macros, no manual re-entry.
STEP 01
Upload
Upload a .docx or .pdf and Smart Import reads the file directly — no conversion, no cleanup required beforehand.
STEP 02
Parse
Smart Import extracts the full document outline — headings, paragraphs, lists, images, and tables — preserving the original structure.
STEP 03
Map & Classify
Map each heading level to a work item type, and classify paragraphs, lists, and tables into the fields they belong to.
STEP 04
Link
Connect imported items to existing work items, parent hierarchies, or requirement sets already in Azure DevOps.
STEP 05
Preview
A pre-import preview flags duplicates, ambiguous items, and missing fields before anything is committed.
STEP 06
Import
Commit the mapped items to Azure DevOps. Open the result directly in Queries or publish it as a Smart Doc.
WHAT YOU GET
Smart Import capabilities that turn documents into structured backlog data
GUIDED WIZARD
One workflow from file to backlog.
Upload, Parse, Map & Classify, Link, Preview, and Import all run inside a single guided wizard — no separate tools, no manual hand-offs between steps.
OUTLINE EXTRACTION
Reads the document the way you wrote it.
Smart Import extracts the full heading structure of a .docx or .pdf, along with paragraphs, lists, images, and tables, preserving the original organization of the source file.
MAP & CLASSIFY
Every heading becomes the right work item type.
Map heading levels to Epics, Features, Requirements, or any custom work item type, and classify body content into the fields it belongs in.
TABLE ROWS TO WORK ITEMS
Turn a table into a backlog in one pass.
Convert table rows directly into individual work items, with each column mapped to a field — ideal for requirement tables, test case tables, and traceability matrices.
CONDITIONAL ROUTING
If/else rules decide where content goes.
Route headings and content using conditional if/else rules based on heading text, level, or pattern, so differently structured sections land in the right place automatically.
LINK & DE-DUPLICATE
Connect to what already exists.
Link imported items to existing work items and parent hierarchies already in Azure DevOps, avoiding duplicate entries for content that's already tracked.
PRE-IMPORT PREVIEW
See problems before you commit.
A pre-import preview flags duplicates, ambiguous mappings, and missing required fields, so nothing gets committed to Azure DevOps until it's right.
QUERIES & SMART DOC OUTPUT
Land exactly where your team works.
Once imported, work items can be opened directly in Queries or published as a Smart Doc — creating a clear path from source document to live backlog.
PRECISION CONTROLS
Every import is reviewed, mapped, and validated before it touches your backlog.
Smart Import gives teams the same level of control over automated imports that they'd expect from manual entry — without the manual effort.
MAP & CLASSIFY RULES
Define the mapping once, reuse it everywhere.
Save heading-to-work-item-type mappings as reusable rule sets so the next document from the same source imports the same way.
CONDITIONAL IF/ELSE
Handle exceptions without a second pass.
Route content differently based on heading patterns, so exceptions in a document don't require manual cleanup afterward.
DUPLICATE DETECTION
Never import the same requirement twice.
The pre-import preview checks new content against existing work items and flags likely duplicates before commit.
FIELD VALIDATION
Missing fields get caught, not shipped.
Required fields left unmapped or unfilled are flagged in preview, not discovered after the import has already run.
TRACEABILITY
Know where every item came from.
Imported work items retain a link back to their source document and section, so origin is never a guess.
REVIEW BEFORE COMMIT
Nothing lands in ADO without your sign-off.
The Preview stage is a hard stop — nothing is written to Azure DevOps until the mapped result has been reviewed and approved.
Reads and imports from
.DOCX.PDFHeadings & StylesNumbered ListsBulleted ListsTablesImagesNested SectionsLegacy Templates
BUILT FOR EVERY ROLE
Every role on your team has a specific reason to use Smart Import
Business analysts, product owners, systems engineers, and program managers — Smart Import fits every seat that touches an existing document.
Analista de negocios
Requirements migration owner
A business analyst imports an existing SRS written in Word directly into Azure DevOps, mapping each heading to a Requirement work item instead of retyping 60 pages of specification by hand.
Responsable de producto
Backlog bootstrap owner
A product owner converts a stakeholder's PDF feature brief into Features and Stories in one pass, using Map & Classify to route each numbered item to the correct work item type.
Systems Engineer
Legacy spec owner
A systems engineer imports a decade-old systems requirements document, using conditional if/else rules to route differently formatted legacy sections into the correct hierarchy level.
Technical Writer
Documentation reconciliation owner
A technical writer imports a supplier's specification document to check it against the existing backlog, using the pre-import preview to catch duplicate requirements before anything is committed.
QA Lead
Test case migration owner
A QA lead imports a table of manual test cases from a Word document, converting each row directly into a Test Case work item with columns mapped to fields.
Responsable de cumplimiento normativo
Standard intake owner
A compliance manager imports a new regulatory standard distributed as a PDF, mapping each clause heading to a Requirement so compliance tracking starts in ADO from day one.
Program Manager
Multi-vendor intake owner
A program manager imports specification documents from multiple vendors, linking each import to the same parent Epic so all vendor requirements roll up under one program view.
Migration Lead
Legacy tool migration owner
A migration lead imports years of accumulated Word-based requirements as part of a move off a legacy requirements tool, using saved mapping rules to process each document the same way.
INDUSTRY USE CASES
Industry specific use cases of Smart Import
See how teams across aerospace, defense, medtech, automotive and finance use Smart Import to bring legacy documents into Azure DevOps without retyping a single requirement.
DO-178C
Systems engineer
DO-178C legacy SRS import
An aerospace systems engineer imports a decade-old Software Requirements Specification maintained in Word, mapping each numbered requirement to a Requirement work item and linking it to the existing Feature hierarchy already in Azure DevOps.
IEC 62304
Regulatory affairs manager
IEC 62304 design history import
A medical device team imports a legacy Software Requirements Specification PDF into the Design History File backlog, with the pre-import preview flagging requirements that already exist to avoid duplicate entries.
ISO 26262
Functional safety engineer
ISO 26262 hazard analysis import
A functional safety engineer imports a HARA document authored in Word, using conditional routing to map Hazardous Event headings to one work item type and Safety Goal headings to another.
EN 50128
Systems safety engineer
EN 50128 table-to-test-case import
A railway systems safety engineer imports a table of verification test cases from a Word appendix, converting each row into an individual Test Case work item mapped by column.
GAMP 5
Validation lead
GAMP 5 URS bulk import
A validation lead imports a User Requirements Specification distributed as a PDF, mapping each numbered clause to a Requirement and linking it to the validation project already set up in Azure DevOps.
NIST SP 800-53
Cloud security controls engineer
NIST control catalog import
A security controls engineer imports a 300-plus control catalog distributed as a formatted Word document, converting each control row into a work item with owner and status fields pre-populated.
SOX Section 404
IT compliance lead
SOX ITGC control import
An IT compliance lead imports an ITGC control document maintained outside ADO, using saved mapping rules so the same document format from every subsidiary imports identically.
Legacy migration
Program manager
RFP response requirements import
A program manager imports a client's RFP requirements document during a bid, converting every numbered requirement into a trackable work item before the proposal team starts scoping.
WHERE TEAMS USE IT
Built for the moment a document has to become a backlog.
MIGRATION
Move off legacy tools without retyping.
Bring years of Word-based requirements into Azure DevOps without manual re-entry, using saved mapping rules to process every document the same way.
COMPLIANCE INTAKE
New standards, tracked from day one.
Import a new regulation or standard the moment it's published, so compliance tracking starts inside ADO instead of sitting in a parked PDF.
VENDOR & RFP INTAKE
Turn a bid document into a backlog.
Convert a client's RFP or a vendor's specification into structured work items before the team starts scoping, with every requirement traceable to its source.
AUDIT PREP
Reconcile documents against the backlog.
Import a specification to check it against what's already in ADO, using the pre-import preview to surface duplicates and gaps before an audit does.
THE IMPACT
Documents that stop costing your team days.
6-step
Guided wizard from raw document to committed Azure DevOps work items
0
Manual re-entry for headings, tables, lists, or images already in the source document
100%
Of imported items traceable back to their source document and section
1-click
Preview to catch duplicates, ambiguous mappings, and missing fields before import
FAQS
Everything you need to know before getting started.
Microsoft Word (.docx) and PDF (.pdf). Smart Import reads the file directly — no conversion or cleanup required beforehand.
You map each heading level to a work item type in the Map & Classify step. Save the mapping as a reusable rule set so future documents in the same format import the same way.
Yes. Conditional if/else routing lets you handle headings and sections that don't follow a consistent pattern, directing them to the correct work item type based on rules you define.
Table rows can be converted directly into individual work items, with each column mapped to a field — useful for requirement tables, test case tables, and traceability matrices.
No. The pre-import preview checks new content against existing work items in the target project and flags likely duplicates before anything commits.
Yes. The Link step lets you connect imported items to existing parent hierarchies or requirement sets already in your ADO project, rather than creating a disconnected set of new items.
Completed imports can be opened directly in Queries for further work, or published as a Smart Doc for a structured document view of the same live data.
Yes. Images in the document outline are extracted and can be attached to the work items they belong to as part of the mapping.
Yes. The Preview stage is a hard stop — nothing commits to ADO until you've reviewed the mapped result and any flagged issues have been resolved.
Yes. Smart Import runs natively as part of Modern Requirements4DevOps NextGen on both Azure DevOps Services and Azure DevOps Server.
GET STARTED
Stop Retyping Requirements. Start Importing Them.
Smart Import is part of Modern Requirements4DevOps NextGen — built natively inside Azure DevOps. Upload a document, map it once, and let the wizard do the re-entry for you.
No migration required · Free trial available · No credit card required · Azure DevOps Server & Services
EXPLORE MODERN REQUIREMENTS4DEVOPS NEXTGEN
Complete Your Requirements Workflow With the Full Modern Requirements4DevOps NextGen
Every feature below connects directly to your Smart Import results — no separate configuration required.
Documentos inteligentes
Turn imported work items into a living, structured document that stays in sync with Azure DevOps automatically.
Explore Smart Docs →Análisis de trazas
Verify that everything you just imported is properly linked, with coverage gaps surfaced before they become audit findings.
Explore Trace Analysis →Informes inteligentes
Generate one-click formatted output from any imported work item set — in Word, PDF, or HTML using your branded templates.
Explore Smart Reports →Gestión de reseñas
Route freshly imported requirements through a formal, multi-stakeholder approval workflow before they're considered final.
Explore Review Management →Línea de base
Freeze the state of your backlog right after a big import, so you always have an immutable snapshot of what came in and when.
Explore Baseline →Version Package Management
Group imported requirements into a formal version package tied to the release or delivery milestone they belong to.
Explore VPM →
