A sprint assigns selected work to a named delivery period. The backlog holds work that is not currently assigned to a sprint in this simplified model. A label that happens to contain a sprint name doesn't establish membership, dates or a sprint goal.
Check the board and sprint state before moving work. A future sprint is planning space; a closed sprint records a completed period and should not accept new work. Moving work into an active sprint can change its scope, so communicate that change instead of hiding it in an estimate. The local engine stores membership and validates the target sprint. It doesn't copy issues when you move them. Keep the issue key stable and verify the saved sprint identifier, especially when two sprint names look similar.
Plan the intended issues using the sprint relationship.