A sprint moves through future, active and closed states. Starting it needs a clear period and goal. Completing it needs a deliberate destination for unfinished work, because a status that looks nearly finished is still unfinished unless it meets the board's completion definition.
Inspect scope before starting the next period. The local model allows one active sprint per board, so close the active period first. During closeout, finished work stays associated with its completed period while unfinished work moves to the chosen future sprint or backlog. Hosted parallel sprints, reports and permissions add more choices. This course doesn't infer a real team's commitment from a display label. Practice the explicit lifecycle actions and verify the resulting sprint state and unfinished membership.
Run a deliberate sprint start and closeout.