diff --git a/docs/initiatives.rst b/docs/initiatives.rst
index 4ad7e9a..878df3d 100644
--- a/docs/initiatives.rst
+++ b/docs/initiatives.rst
@@ -10,13 +10,13 @@ Drafts
 .. toctree::
     :maxdepth: 1
 
-
 Completed review
 ----------------
 
 .. toctree::
     :maxdepth: 1
 
+    pagure2forgejo/index
     dist-git-comparison/index
     dist-git-move/index
     dnf-countme/index
diff --git a/docs/pagure2forgejo/index.rst b/docs/pagure2forgejo/index.rst
new file mode 100644
index 0000000..a125ffc
--- /dev/null
+++ b/docs/pagure2forgejo/index.rst
@@ -0,0 +1,70 @@
+Pagure to Forgejo Importer
+==========================
+
+Purpose
+-------
+
+With Fedora Project deciding on moving over to Forgejo as the new git forge, it
+is important to devise a convenient method with which project maintainers can migrate
+their repository assets and issue tickets to a Forgejo namespace maintained by the
+Fedora Infrastructure.
+
+Resources
+---------
+
+- Initiative proposal: https://pagure.io/fedora-infra/infrastructure-projects/issue/3
+- Tracking ticket: https://pagure.io/fedora-infra/forgejo-deployment/issue/10
+- Pagure documentation: https://docs.pagure.org/pagure/#
+- Forgejo API documentation: https://codeberg.org/api/swagger
+- Fedora Moves Towards Forgejo: https://fedoramagazine.org/fedora-moves-towards-forgejo-a-unified-decision/
+- Fedora Chooses Forgejo: https://communityblog.fedoraproject.org/fedora-chooses-forgejo/
+
+Requirements
+------------
+
+Same as the requirements for `Pagure Exporter <https://fedora-arc.readthedocs.io/en/latest/pagure2gitlab/index.html#requirements>`__.
+
+Nice to haves
+-------------
+
+Same as the nice to haves for `Pagure Exporter <https://fedora-arc.readthedocs.io/en/latest/pagure2gitlab/index.html#nice-to-have>`__.
+
+Investigation
+-------------
+
+Following are the investigations of importing repository assets and issue tickets
+from Pagure to Forgejo.
+
+.. toctree::
+    :maxdepth: 1
+
+    repo
+    tkts
+
+Conclusions
+-----------
+
+As this proposal would very likely make use of the same foundations that were
+already established with the previously
+`investigated <https://fedora-arc.readthedocs.io/en/latest/pagure2gitlab>`_ and
+`implemented <https://github.com/fedora-infra/pagure-exporter>`_ project, it is
+strongly recommended to implement this project as being an extension to the
+existing project instead of recreating the foundations of the project again from
+the ground up.
+
+Proposed Roadmap
+----------------
+
+1. Add a command line option to segregate options for GitLab and Forgejo support
+2. Implement the issue tickets transfer in the command line utility
+3. Implement the repository assets transfer in the command line utility
+4. Ensure that the project codebase has a healthy coverage of functional tests
+5. (Optional) Create a CI bot for reliably automating the migration process
+6. Prepare the documentation for development and usage purposes for the tool
+7. Make releases for Fedora Linux repositories for RPM and PyPI for containers
+8. Announce the general availability of the project on community platforms
+
+Estimate of work
+----------------
+
+This work will need 2 developers. The estimation for this project is 4 weeks.