diff --git a/apps/emqx_management/src/emqx_mgmt_auth.erl b/apps/emqx_management/src/emqx_mgmt_auth.erl
index afa8a8e2e..ab2a57972 100644
--- a/apps/emqx_management/src/emqx_mgmt_auth.erl
+++ b/apps/emqx_management/src/emqx_mgmt_auth.erl
@@ -262,7 +262,9 @@ maybe_cleanup_api_key(#?APP{name = Name, api_key = ApiKey}) ->
         [_App1] ->
             ?SLOG(info, #{
                 msg => "update_apikey_name_from_old_version",
-                info => <<"Update ApiKey name with new name rule, more information: xxx">>
+                info =>
+                    <<"Update ApiKey name with new name rule, see also: ",
+                        "https://github.com/emqx/emqx/pull/11798">>
             }),
             ok;
         Existed ->
diff --git a/changes/ce/fix-11798.en.md b/changes/ce/fix-11798.en.md
new file mode 100644
index 000000000..94442d185
--- /dev/null
+++ b/changes/ce/fix-11798.en.md
@@ -0,0 +1,5 @@
+Fixed the issue where the node could not start after executing `./bin/emqx data import [FILE]`.
+
+And strongly bind apikey's `apikey_key` to `apikey_name`.
+- `apikey_key` will generate a unique value from the given human-readable `apikey_name` when generating an apikey using dashboard.
+- `apikey_name` will be a unique value generated by `apikey_key` when using bootstrap file to generate apikey, .