Add Ghidra import documentation

Author: negasora

docs/guide/migration/ghidra/ghidraimport.md

@@ -0,0 +1,23 @@
+# Ghidra Import
+
+Currently, the following categories of analysis information can be imported from Ghidra files:
+
+- Types
+- Memory map
+- Data variables
+- Functions
+- Comments
+- Bookmarks
+
+## Importing data
+### Import to a new file
+`Plugins > Ghidra Import > Open Database...` allows you to select a Ghidra file to open as a binary view in Binary Ninja. You are able to select a single `.gbf` file or project file from a `.gpr`.
+
+### Import to an existing file
+`Plugins > Ghidra Import > Import Database...` allows you to apply analysis information from a Ghidra file to an already open binary view in Binary Ninja. You are able to select a single `.gbf` file or project file from a `.gpr`. You can choose to import all or only some categories of analysis information to apply to the binary view.
+
+### Import to an existing project
+!!! note
+    Binary Ninja projects are only available in Commercial and Ultimate editions
+
+`Plugins > Ghidra Import > Import Project...` allows you to import files from a Ghidra project (`.gpr`) to an open Binary Ninja project. All available analysis information will be imported for all selected files.

docs/guide/migration/migrationguideghidra.md renamed to docs/guide/migration/ghidra/index.md

@@ -2,22 +2,26 @@
 
 ## Starting Binary Ninja
 
-Binary Ninja starts with the [New Tab Page](../index.md#new-tab) open. From here, you can optionally [start a project](../projects.md#creating-a-project) to work with multiple files, navigate your offline docs from the help menu, or just [open existing files](../index.md#loading-files) (including drag-and-drop!).
+Binary Ninja starts with the [New Tab Page](../../index.md#new-tab) open. From here, you can optionally [start a project](../../projects.md#creating-a-project) to work with multiple files, navigate your offline docs from the help menu, or just [open existing files](../../index.md#loading-files) (including drag-and-drop!).
 
 ## Decompiler Settings
 
 Binary Ninja likes to stay out of your way as much as possible, but sometimes you need to dig into the settings and change how a file is analyzed. If you have a file that can be opened with default settings, you won't get prompted for any additional input. Binary Ninja will automatically analyze the entire file — including running [linear sweep](https://binary.ninja/2017/11/06/architecture-agnostic-function-detection-in-binaries.html) — and provide you with linear decompilation for the whole file (like Ghidra's linear disassembly, but as decompilation by default).
 
-If you're opening a [Universal Mach-O](https://en.wikipedia.org/wiki/Universal_binary), the Open with Options dialogue will appear so that you can choose which architecture to open (in the top right). If you have a default architecture you want to open whenever you open a universal binary, you can set your preference in a setting called [Universal Mach-O Architecture Preference](../settings.md#settings-reference). You'll also see the Open with Options dialogue when Binary Ninja is unable to recognize the file type or otherwise needs user input to analyze the file (can't find the entry point, needs you to provide some memory mappings, etc.).
+If you're opening a [Universal Mach-O](https://en.wikipedia.org/wiki/Universal_binary), the Open with Options dialogue will appear so that you can choose which architecture to open (in the top right). If you have a default architecture you want to open whenever you open a universal binary, you can set your preference in a setting called [Universal Mach-O Architecture Preference](../../settings.md#settings-reference). You'll also see the Open with Options dialogue when Binary Ninja is unable to recognize the file type or otherwise needs user input to analyze the file (can't find the entry point, needs you to provide some memory mappings, etc.).
 
-It's worth digging into Binary Ninja's [settings](../settings.md) and seeing what's available to tune, but if you ever want to change a setting for a single binary, you can Open (it) with Options. Go to File -> Open with Options, and any settings you change will apply to only that file.
+It's worth digging into Binary Ninja's [settings](../../settings.md) and seeing what's available to tune, but if you ever want to change a setting for a single binary, you can Open (it) with Options. Go to File -> Open with Options, and any settings you change will apply to only that file.
 
 <!-- TODO : Can you analyze a file while Ghidra is running its analysis?
 ## Analyzing While Analyzing -->
 
+## Importing Data
+
+See [the Ghidra import documentation](./ghidraimport.md)
+
 ## Keybindings
 
-Binary Ninja's keybindings are very different from Ghidra. Thankfully, [Binary Ninja's action system](https://binary.ninja/2024/02/15/command-palette.html) allows you to easily find actions and view the keybindings extremely easily. It'll also save you from digging through unfamiliar right-click menus while helping you learn any new keybindings. All actions can have their keybinding set, changed, or removed in the [keybindings menu](../index.md#default-hotkeys).
+Binary Ninja's keybindings are very different from Ghidra. Thankfully, [Binary Ninja's action system](https://binary.ninja/2024/02/15/command-palette.html) allows you to easily find actions and view the keybindings extremely easily. It'll also save you from digging through unfamiliar right-click menus while helping you learn any new keybindings. All actions can have their keybinding set, changed, or removed in the [keybindings menu](../../index.md#default-hotkeys).
 
 Some of the most useful default keybindings are as follows:
 
@@ -69,21 +73,21 @@ Binary Ninja's layout is also a bit different from what you're used to in Ghidra
 
 ## Cross-References
 
-![xref icon >](../../img/xref-icon.png "Xref Icon")
+![xref icon >](../../../img/xref-icon.png "Xref Icon")
 
 If you prefer the pop-up style cross-references from IDA or Ghidra, you can enable that behavior by right-clicking on the xref-icon and selecting "Window". Whenever you navigate from the window by double-clicking or pressing enter the main window will be focused. ESC can also be used to close the xref window.
 
 ### Theme
 
-This doesn't exactly have to do with your layout, but it go a long way towards making the interface feel a bit more familiar. We have an expansive list of [community themes](https://github.com/Vector35/community-themes), and [a guide](../../dev/themes.md) and a [blog post](https://binary.ninja/2021/07/08/creating-great-themes.html) on how to make your own. The built-in "Classic" theme should feel nostalgic, but if you're looking for a light theme that's slightly easier on the eyes, try out Summer or Solarized Light.
+This doesn't exactly have to do with your layout, but it go a long way towards making the interface feel a bit more familiar. We have an expansive list of [community themes](https://github.com/Vector35/community-themes), and [a guide](../../../dev/themes.md) and a [blog post](https://binary.ninja/2021/07/08/creating-great-themes.html) on how to make your own. The built-in "Classic" theme should feel nostalgic, but if you're looking for a light theme that's slightly easier on the eyes, try out Summer or Solarized Light.
 
 ### Feature Map
 
-Binary Ninja's [feature map](../index.md#feature-map) lives on the right side of your main view area. If you'd rather not see it, you can right-click it and select "Hide Feature Map."
+Binary Ninja's [feature map](../../index.md#feature-map) lives on the right side of your main view area. If you'd rather not see it, you can right-click it and select "Hide Feature Map."
 
 ### Sidebars
 
-Our sidebars have a whole host of customization options, so make sure to check out [their dedicated docs](../index.md#the-sidebar) to maximize your workflow.
+Our sidebars have a whole host of customization options, so make sure to check out [their dedicated docs](../../index.md#the-sidebar) to maximize your workflow.
 
 That said, I'll walk you through how to set up your sidebars to get it looking very similar to what you're used to in Ghidra.
 
@@ -115,8 +119,8 @@ Now that you've done all this hard work to make the perfect layout, it would be
 
 ...about switching to Binary Ninja! We know leaving your old tool behind can be hard, and there will be things you miss, but we think there are a lot of features packed into Binary Ninja that you'll love. Here are a couple we think you'll appreciate:
 
- - [Updates every day](../index.md#updates) on the dev branch (nearly) - accepted PRs can be in everyone's hands within hours.
- - [Our awesome native Python API](../../dev/cookbook.md) (and [C++](https://api.binary.ninja/cpp/), and [Rust](https://dev-rust.binary.ninja/))
+ - [Updates every day](../../index.md#updates) on the dev branch (nearly) - accepted PRs can be in everyone's hands within hours.
+ - [Our awesome native Python API](../../../dev/cookbook.md) (and [C++](https://api.binary.ninja/cpp/), and [Rust](https://dev-rust.binary.ninja/))
  - [The speed](https://binary.ninja/2022/05/31/3.1-the-performance-release.html)
  - ...not needing to manage Java installations
 

docs/guide/migration/index.md

@@ -10,7 +10,7 @@ We have quick start guides for the following:
 
 - [New Users](../../getting-started.md)
 - [IDA Pro Users](migrationguideida.md)
-- [Ghidra Users](migrationguideghidra.md)
+- [Ghidra Users](./ghidra/index.md)
 
 ## Additional Resources
 

docs/guide/settings.md

@@ -244,6 +244,7 @@ The setting will appear under the Quick Settings section in the Function Setting
 |corePlugins|DWARF Import Plugin|Enable the DWARF import plugin.|`boolean`|`True`|[`SettingsUserScope`]|<a id='corePlugins.dwarfImport'>corePlugins.dwarfImport</a>|
 |corePlugins|EFI Resolver|Enable the built-in EFI Resolver plugin.|`boolean`|`True`|[`SettingsUserScope`]|<a id='corePlugins.efiResolver'>corePlugins.efiResolver</a>|
 |corePlugins|Firmware Ninja|Enable the Firmware Ninja plugin.|`boolean`|`True`|[`SettingsUserScope`]|<a id='corePlugins.firmwareNinja'>corePlugins.firmwareNinja</a>|
+|corePlugins|Ghidra Import Plugin|Enable the built-in Ghidra import plugin.|`boolean`|`True`|[`SettingsUserScope`]|<a id='corePlugins.ghidraImport'>corePlugins.ghidraImport</a>|
 |corePlugins|IDB Import Plugin|Enable the IDB import plugin.|`boolean`|`True`|[`SettingsUserScope`]|<a id='corePlugins.idbImport'>corePlugins.idbImport</a>|
 |corePlugins|PDB Import Plugin|Enable the built-in PDB import plugin.|`boolean`|`True`|[`SettingsUserScope`]|<a id='corePlugins.pdbImport'>corePlugins.pdbImport</a>|
 |corePlugins|Stack Render Layer Plugin|Enable the built-in Stack Render Layer plugin.|`boolean`|`True`|[`SettingsUserScope`]|<a id='corePlugins.stackRenderLayer'>corePlugins.stackRenderLayer</a>|
@@ -582,4 +583,4 @@ The setting will appear under the Quick Settings section in the Function Setting
 |warp.matcher|Minimum Function Length|Functions below this length will not be matched.|`number`|`0`|[`SettingsProjectScope`, `SettingsResourceScope`, `SettingsUserScope`]|<a id='warp.matcher.minimumFunctionLength'>warp.matcher.minimumFunctionLength</a>|
 |warp.matcher|Minimum Matched Constraints|When function constraints are checked the amount of constraints matched must be at-least this.|`number`|`1`|[`SettingsProjectScope`, `SettingsResourceScope`, `SettingsUserScope`]|<a id='warp.matcher.minimumMatchedConstraints'>warp.matcher.minimumMatchedConstraints</a>|
 |warp.matcher|Trivial Function Adjacent Constraints Allowed|When function constraints are checked if this is enabled functions can match based off trivial adjacent functions.|`boolean`|`False`|[`SettingsProjectScope`, `SettingsResourceScope`, `SettingsUserScope`]|<a id='warp.matcher.trivialFunctionAdjacentAllowed'>warp.matcher.trivialFunctionAdjacentAllowed</a>|
-|warp.matcher|Trivial Function Length|Functions below this length in bytes will be required to match on constraints.|`number`|`20`|[`SettingsProjectScope`, `SettingsResourceScope`, `SettingsUserScope`]|<a id='warp.matcher.trivialFunctionLength'>warp.matcher.trivialFunctionLength</a>|
+|warp.matcher|Trivial Function Length|Functions below this length in bytes will be required to match on constraints.|`number`|`20`|[`SettingsProjectScope`, `SettingsResourceScope`, `SettingsUserScope`]|<a id='warp.matcher.trivialFunctionLength'>warp.matcher.trivialFunctionLength</a>|

mkdocs.yml

@@ -111,7 +111,9 @@ nav:
         - Migration Guide:
             - 'guide/migration/index.md'
             - Migrating from IDA: 'guide/migration/migrationguideida.md'
-            - Migrating from Ghidra: 'guide/migration/migrationguideghidra.md'
+            - Migrating from Ghidra:
+                - 'guide/migration/ghidra/index.md'
+                - Ghidra Import: 'guide/migration/ghidra/ghidraimport.md'
         - Types:
             - 'guide/types/index.md'
             - Basic Types: 'guide/types/basictypes.md'