TruSpec Virtual Solutions · Migration Readiness Report
Contoso Retail: Online Store
Recommendation: a managed migration
2 parent items have more than 100 children. These need restructuring decisions a managed migration takes care of.
Executive summary
A enterprise migration: best done as a managed project
This Azure DevOps project holds 14,212 work items (7,480 tasks, 3,915 user stories, 2,140 bugs), worked on by 86 people. We rate the move to GitHub as Enterprise.
One finding needs a decision before moving: 2 parent items have more than 100 children. Everything else carries over with BoardBridge's standard mapping.
Once started, the migration runs unattended for about 6 days; your team keeps working in Azure DevOps until the final cut-over. Because of the points above, we recommend a managed migration: TruSpec plans the mapping with you, runs the migration and checks the result.
Next steps
- Book a 30-minute consultation to go through the findings.
- Receive a fixed-price proposal for the managed migration.
- Agree a cut-over date with your team.
Nothing from this scan was sent to an AI service.
What needs attention
GitHub allows up to 100 sub-issues under one issue; the largest here has 143. Those parents need regrouping (for example an extra level of features) before or during the migration.
Legacy Ticket Id: their values can be kept as text in each issue's description, but not as fields you can filter on.
Release Notes, Product Owner, Compliance Review: yes/no, long text, people and path fields become a pick-list, a section of the description, an assignee or a text field.
Service accounts, build services and sign-ins without an email address need mapping by hand, or their work is credited to a placeholder.
Former team members' history is kept, but they may not have GitHub accounts in your organization. Decide whether to map them or show their names only.
The largest is 212.0 MB. GitHub doesn't accept files that big on issues; they stay as links to Azure DevOps, and 4 files are over 100 MB, too big to copy into a repository.
1 custom work item type, 3 changed built-in types and 6 custom states. BoardBridge's mapping screen handles these; check the suggested mapping.
82 links point to other projects. They're kept as links back to Azure DevOps unless those projects move too.
8,640 development links point to Azure Repos or Pipelines. They're listed in each issue; GitHub links only its own commits and pull requests.
What we found
| Work items | 14,212 (3,904 open) |
|---|---|
| Work item types | 6 |
| Hierarchy | 5 levels deep; up to 143 children under one item |
| Attachments | 6,210 (9.4 GB; largest 212.0 MB) |
| Comments | 41,870 |
| People | 86 (23 inactive for 6 months; 5 to map by hand) |
| Iterations and areas | 74 iterations (71 with dates), 19 areas |
| Custom fields in use | 9 (5 map to GitHub fields) |
| Process | Contoso Agile (inherited; customization: light) |
| Revision history | 312,400 revisions |
| Links | 2,930 related, 1,105 dependencies, 8,640 to code or builds, 64 to other projects |
Work items by type
Custom fields
| Field | Type | In GitHub | Used on |
|---|---|---|---|
| Customer Impact | string | Project field | 5,120 items |
| Release Train | string | Project field | 4,870 items |
| Store Region | string | Project field | 3,310 items |
| Business Value | integer | Project field | 3,090 items |
| Go-Live Date | dateTime | Project field | 980 items |
| Release Notes | html | Needs a choice | 1,460 items |
| Product Owner | identity | Needs a choice | 2,210 items |
| Compliance Review | boolean | Needs a choice | 640 items |
| Legacy Ticket Id | guid | Text in the issue | 1,905 items |
Measured 2026-10-12 with a read-only token; only counts were kept. Attachments total 9.4 GB. The migration time uses the same estimate as BoardBridge's dry run: GitHub limits how fast issues and comments can be created, so large projects run unattended for hours or days.