Implementation FAQ

Data Migration and Preparation

What materials are provided to the customer to start the data migration process?

Implementation team will send import templates and implementation documents covering properties, residents, and system configuration. These templates detail both the required and optional fields for both property and resident sections

What is the timeline for data submission?

The data submission timeline requires data to be submitted 30 days prior to installation

Who is responsible for compiling the existing resident data?

The customer e.g. board/property management team is responsible for compiling existing resident data and delivering to Proptia for import into the software.

What is critical regarding address formats during the data import?

It is essential to ensure that address formats match between the Properties and Residence tabs for proper data linking

How will the system handle multiple residents per property?

The system is configured to handle multiple residents per property

How is License Plate Recognition (LPR) data entered into the system?

LPR data will need to be manually entered into the resident profiles

Should we import existing visitor management data?

It is recommended that the community start fresh for visitor management rather than importing existing data from the previous platform, as communities often struggle with managing outdated visitor records

Access Control and Credentials

What are the default access levels assigned to residents during the initial import?

All residents will be imported with two access levels by default: one for vehicle gates and one for pedestrian gates. The system allows for adding future access levels without additional work.

What credentials are recommended for resident access?

For vehicle access: RFID, Bluetooth, LPR. For pedestrian access e.g. on foot into doors, buildings, and amenities: Bluetooth credentials over fobs. 

Can existing RFID tag data be imported from the prior platform?

Yes you will need to extract existing credential data (e.g., RFID tag data) from your existing system. 

System Configuration

Are PIN codes advised for the Telephone Entry System?

No due to security concerns. PIN codes can easily be shared. 

How is the system configured to handle different resident groups?

Resident and member data can be organized into different groups (such as golf, pool/tennis, and social) with the possibility of assigning separate management access levels if required

What is the purpose of the verbal confirmation code feature?

The verbal confirmation code feature allows residents to validate guest additions when they are unable to access the system themselves

How is the ``Associate Resident`` feature used?

The Associate Resident feature allows additional household members—such as a son, daughter, nanny, or grandparent—to be added under the primary resident’s profile. Each associate can be tagged with their relationship to the primary resident and, if permitted, can have the same access rights and the ability to manage a visitor list.

Associate residents can be added by management, or the system can be configured to allow primary residents to add them directly.