Hey @bythewiseman!
This was a bug that was found in the migration for the versions of Forms released yesterday (both 17.6. and 18.2).
Patch versions have just been released (17.6.1 and 18.2.1) that resolve this issue and can be safely applied without any database changes to the umbracoKeyValue table.
If you have any more issues with it, please reply and we can escalate it / get a GitHub issue raised