Pre-Migration Preparation

What Integrators must complete as part of the Property Assessment & Requirements Gathering

1. Device Review

Firmware Verification

• Review firmware versions on all devices against minimum requirements. All devices must meet minimum firmware before migration to ensure optimal performance.

!Critical: Firmware updates must be completed before final device sync. The minimum firmware version supports HMAC, and syncing with Engage afterward enables HMAC efficiently. Without HMAC enabled, Zentra app will be unable to sync with locks post-migration.

Device Sync Status

• Record last sync date for all devices. If devices haven’t synced since January 2024, we recommend that devices be sync’d before migration. This ensures latest audits are captured and HMAC authentication is properly enabled, and will allows the day of migration activities to be completed more quickly.

Wireless Device Assessment

• NDE, NDEB, LE, LEB, CTE wireless devices require special attention. Review Engage audits to verify devices are actively checking in regularly. This helps us confirm Wi-Fi connectivity for devices operating in online mode is functioning before the migration day.

• Note: Wireless devices will receive new default check-in times after import

Enrollment Reader Requirements

• Confirm ethernet drop available at desired credential programming location as the Schlage RC will be added as enrollment reader post-migration.

2. Credential Assessment

Credential Type Compatibility

Verify property uses supported credential types:

• MiFARE Classic
• DESFire EV1
• DESFire EV3
• Multi-tech versions of above
  

Mobile Credentials

If property uses Schlage mobile credentials:

• Existing credentials will continue functioning until user access changes or device changes
• New phone = new Zentra mobile credential required
• Post-migration: Only Zentra mobile credentials can be created (no new Schlage mobile credentials)

User & Credential Expiration

• Engage automatically applies user expiration dates to profiles, and Zentra does not support that. After the import, all user expirations will be removed. If the property wants to maintain users by expiration dates, they will need to update the credential to be expired, through the use of Special Properties.

3. Pass-Through (formerly known as Master) Credentials

Current Engage ‘Master’ Credentials

• Engage ‘Master’ credentials do NOT migrate correctly automatically. Any Engage user with ‘Master’ selected must have every device individually added to their profile This ensures all devices are migrated to Zentra with that access

New Pass-Through Credentials

• If property requires NEW pass-through credentials, create these in Zentra before the syncing of devices on Migration day. These must be manually created and imported post-migration. Pass-through credentials require sync with each lock to add/remove (no device group support for Control locks)

4. Site Organization & Cleanup

Device Naming

• Review all device names for duplicates – duplicates will cause import failure
• Ensure device names meet Zentra requirements:
  • 1-20 characters (Engage allows up to 25)
  • Letters, numbers, and symbols (#, -, and spaces) only
  • Cannot start or end with spaces
  • No special characters beyond those listed

!During the import, device names that are outside the Zentra requirements will be successfully imported. But if they need to change anytime in the future, the Zentra limitations will apply.

Site Structure Review

• Review devices, schedules, and user groups
• Rename items as needed for clarity and ease of access management
• Apply best practices for naming conventions

5. Reporting & Documentation

Pre-Migration Reports

• Export audit history from Engage if property requires historical records
• Once migrated, Engage audits cannot be retrieved
• Run any required reports on credential expirations and system status