Cards are not migrated. They will work until the legacy place is deprecated. Then they will have to be moved to the organization (we can probably automate this too, now it's manual).
Event webhooks and user import integrations are not migrated.
Past events are not migrated - can be exported.
All new events will be attached to the organization, no matter what method was used to sign in (sso vs legacy).
The organization must be put on the new standardized plan within 2 weeks. The migrated legacy place should be deactivated at the same time.
Does profile image pull from SSO (Google, Azure) work?
We don’t currently support it for Google directory. I understand that it is a security issue, and we will add the ability to set the images soon.
Does a card need to be removed from the old organization before it can be added to the new one?
Yes, for now. We’re looking for a solution but it has to be secure.
Do I need to remove the google provisioning integration from the old organization before I add the new one?
It’s not necessary to remove the integration, however we recommend to do it anyway. As both of the accounts are still functioning, there is a risk of creating discrepancies between the old and new places. For example, if you change restrictions only in one place, the imported users might get more access rights through another place. That’s the reason we recommend to keep the old place in the same state as it was at the moment of the migration.
We have the Schlage wireless locks in our office. It says that event webhooks will not be migrated. What can we do?
Webhooks are not affecting wireless locks.
Can multiple company SSO's be supported?
At the moment there can be one SSO integration per organization only.