Moving from Jira and Tempo to Azure DevOps

When a team moves its work from Jira to Azure DevOps, the issues can be migrated, but Tempo Timesheets is a Jira app and its worklogs stay in Jira. Azure Boards has no timesheet of its own, so the hours history and the weekly approval routine are usually the first things lost.

What to keep

Each person's past hours, on the work item they belong to.
The weekly timesheet, submitted and approved by a lead.
Reports by person, area path and iteration, exported to CSV for payroll or invoicing.

Importing Tempo hours with Saguaro Hours

In Tempo, open a report covering the dates you want, and export it as CSV.
In Azure DevOps, open Boards, Timesheet, and the Import from Tempo tab.
Choose the CSV file. It is read in your browser and never uploaded anywhere. Saguaro Hours recognises the usual Tempo columns, and asks which date order the file uses when it cannot tell.
Pick your own name from the Tempo authors in the file (each person imports their own history), and map each Jira issue key to an Azure DevOps work item ID (for example PROJ-142 = 3071).
Preview the entries, then import. Rows that are already in your timesheet (same work item, day, hours and note) are skipped, so running the import twice does not double your hours.

After the import, the same people log new time from the work item form or the weekly grid, submit their week, and the approver approves it.

Time entries are stored in your own Azure DevOps organization, in the extension data storage Microsoft provides. I do not run a server that holds them.

Get Saguaro Hours on the Visual Studio Marketplace. Free for up to 5 people; $4 per user per month above that.

More guides

Also for Azure DevOps: Excel Round-Trip, edit Azure Boards work items in Excel on Windows, Mac or the web, with a diff before saving.