Content Comparison

Way to pull data

Using developer API

Details

Github data can be perceived in terms of the follow hierarchy, You have organization at the top followed by repositories. Each repository has issues, comments and attachments. There are labels which can cut across different issue belonging to different repositories. Milestones belong to repository and there could be organization wide projects too shared by multiple repositories.

Pros

We can generate a report and cross verify the migrated data manually. We can hand over this report with ids of each entity to client so that they can cross verify at their end too.
We can have more control over what information we have to pull from Github
We will have access to unique ids for each entity in Github so that if something fails then we can identify what has exactly failed.

Cons

Extra effort is required to implement such a bridge to pull data from Github and generate a CSV file that Jira can understand
It is not possible to get the attachments using the api

Apis required for migration

GET /orgs/:org - get organization details by Id
GET /repos/:owner/:repo - get repositories by owner and repository id
GET /repos/:owner/:repo/issues - get issues of a repository
Most of this api have links in thir responses to the object we need