# GitHub Issues Migration is coming soon **URL:** \ **Category:** Core Development\ **Created:** [February 18, 2022, 8:54pm UTC](https://discuss.python.org/t/github-issues-migration-is-coming-soon/13791 "2022-02-18T20:54:54Z")\ **Posts on this page:** 1\ **Showing post:** 19
**Author:** ![steve.dower](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/steve.dower/32/56_2.png) [@steve.dower](https://discuss.python.org/u/steve.dower)\ **Post date:** [February 22, 2022, 2:29pm UTC](https://discuss.python.org/t/github-issues-migration-is-coming-soon/13791/19 "2022-02-22T14:29:46Z")
> [@ezio-melotti](#): > > unless we decide to import a smaller subset first (e.g. only the open/active issues) and open up the issues to everyone while the older issues are still being transferred (this is possible, but will mess up the ID order). The closed IDs aren’t going to be useful anyway though, right? All existing commits and NEWS items will still have to go through bpo anyway, or is there some redirection mapping that will handle that? While there’s always some amount of further discussion on closed issues, the vast majority are never going to be touched again. Why recreate them? --- _[View the full topic](https://discuss.python.org/t/github-issues-migration-is-coming-soon/13791)._