Any gotchas upgrading to v4?

[nhe]

I have a legacy frame.io account that’s our company’s daily driver. I’ve rebuilt our automation tooling for the v4 API (though it is still missing some important features that require filthy scraping workarounds… ).

I think I’m ready to move over.

Has anyone had any problems updating their existing legacy account to v4?

Is that an ok workflow or is it recommended to create a new account from scratch? (This would be doable for me but quite annoying, as ongoing projects would mean straddling 2 accounts for some time).

Do existing share links/review links persist ok, including settings like downloads being enabled? Anything else to watch for?

[CharlieAnderson]

hi @nhe you can find more about what to expect when migrating to V4 hereL What to expect when updating to V4: A comprehensive guide for updating your account on a Free, Pro, or Team Plan | Frame.io V4 Knowledge Center

Also, we just updated the migration guide on our docs to be as up to date as possible, so feel free to look that over to see if there’s something that’s been addresses. Anonymous user name is being discussed internally atm.

[nhe]

Reached out to support, but any insights in the meantime? Anybody hit this issue upon trying to update to v4?

EDIT: They actually responded super quickly on the night before Good Friday . Account was flagged for using v3-exclusive features (likely API) and required manual override / consent to update.