I just added Gitlab as a new remote, and pushed. Easy as that. Keeps the entire repo history. I then just removed my old Github remotes.

Thank git for a model that 'allow' migration through a primitive operation.

Apart from the other methods mentioned here (such as the import from the user interface http://doc.gitlab.com/ce/workflow/importing/README.html) is also an import rake task http://doc.gitlab.com/ce/raketasks/import.html for administrators.

If you move your repository by importing it (in GitLab UI, under new project) or just by clone + pushing it yourself, you will always retain your entire commit history.

If you import from GitHub, your issues, PRs, wiki and all code will be imported.

It would be really cool if GitHub stored issue, PR, and wiki information in the main Git repo. That way all of these things would be very easy to keep in sync across different services.

I've had this idea for a while now. I wonder if it would be practical and if anyone has ever tried something like this.

As a separate root branch, it would work nicely. There are huge benefits also in that you get an inspectable history of issues. From GitHub's perspective, it would be more difficult to authenticate issue changes—they'd need signed commits and pre push validation, right?

That's what Joey Hess' github-backup does: https://github.com/joeyh/github-backup

It's one way, though, you can't create a new Issue or PR by just updating repo.

That would be cool, we're discussing distributed code review and issues in https://gitlab.com/gitlab-org/gitlab-ce/issues/4084

Is there an issue/PR migration path as well?

If you use our GitHub importer, it will migrate your code, wiki, issues and PRs. It can do it in batch for all your GH projects.

Docs here: http://doc.gitlab.com/ce/workflow/importing/import_projects_...