This PR changes the logic of the existing migration (described in #3704 )
This fix is done in the actual migration because
If the current migration has already been run, there is nothing for a brand new migration to do
If the current migration hasn't been run, running it will cause data loss. We could no-op the existing migration, but that would just mean a second migration with complex logic to determine which version of the current migration (broken or no-op) had been run.
This PR changes the logic of the existing migration (described in #3704 ) This fix is done in the actual migration because
This closes #3704