Can we migrate plugin suggestion requests instead of closing?

Question

My understanding on the migration policy from site-to-site is the site that a Q&A would be migrated to must be graduated and the question can not be older then a few months.

That said, when we get plugin requests can we just migrate them to Software Recommendation SE? It would appear based on their WordPress tag that they allow them instead of just closing them.

I think migrating instead of closing would be more helpful, as it seems once questions have been downvoted and closed, the user doesn't return (from possible intimidation) - even though that is not the intent.

When trying to leave a comment informing the user these types of questions aren't in scope, it seems some users do not understand the separation - and that leads to frustration.

Some sample plugin questions:

• Responsive Slider Plugin supporting WP Native Galleries, Srcset, Lazy Load?
• custom intro-box plugin similar to author box style with per post customizable title, desc, image & social links
• Suggestion for plugins for content scheduling + pay per publishing

If we do choose this approach, would we also modify the close reason?

Answer 1

We can send such questions to Software Recommendations (SR), but we should be very careful, and we should not add SR to the existing list of migration sites in that close reason.

SR is expecting a certain quality from these questions, outlined here:

What is required for a question to contain “enough information”?

What we can do: We ask the OP to edit the question while it is still on our site until it fits these requirements. Then we can migrate it.

We are not the first site with that problem. See Where to ask for app recommendations? for a similar discussion.

Answer 2

I am not sure what you are asking which is not already possible?

There is a "close > Off-topic > This question belongs on another site in the Stack Exchange network" path.

Though I must note that it is notoriously hard to make good migrations without being closely acquainted with the target stack. For example it took us a while to get finer points of our scope through to Stack Overflow. :)