---
title: How does the ElevateOS & Onesite / Realpage integration work?
description: Learn about the Onesite / Realpage &amp; Elevated Living integration
---

[Skip to content](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#main-content)

English

Show submenu for translations

![Elevate OS Logo (2)](https://help.elevateos.com/hs-fs/hubfs/REBRAND/Elevate%20OS%20Logo%20(2).png?width=200&height=133&name=Elevate%20OS%20Logo%20(2).png)

- [Default HubSpot Blog](http://blog.elevatedliving.com/blog)

Open main navigation

Close main navigation

- [Default HubSpot Blog](http://blog.elevatedliving.com/blog)
- English
  
  Show submenu for translations
- Go to app.elevatedliving.com

 Go to app.elevatedliving.com

 Hello. How can we help you?

- There are no suggestions because the search field is empty.

1. [Customer Success Portal](https://help.elevateos.com/?hsLang=en)
2. [Integrations](https://help.elevateos.com/integrations?hsLang=en)
3. [PMS - Onesite / Realpage](https://help.elevateos.com/integrations?hsLang=en#pms-onesite-realpage)

# How does the ElevateOS & Onesite / Realpage integration work?

## Learn about the Onesite / Realpage & ElevateOS integration

This guide explains how ElevateOS works with RealPage OneSite: what syncs, how to connect a building, how to use it day to day, and what to check when something does not look right.

**Who this is for:** property management teams, on-site staff, RealPage administrators and IT.  
**Using Yardi instead?** See the [Yardi Integration User Guide](https://claude.ai/artifact/DGUee6MCPaNc3nZNL5Eetg).

### In this article

- [Overview](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#overview)
- [Requirements](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#requirements)
- [Initial setup](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#setup)
- [Sync schedule](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#sync)
- [Residents and accounts](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#residents)
- [Maintenance and work orders](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#work-orders)
- [Checklists, inspections, pets and vehicles](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#checklists)
- [Rent payments](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#payments)
- [Changing your connection](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#changes)
- [Troubleshooting](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#troubleshooting)
- [FAQ](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#faq)
- [What RealPage does and does not do](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#limits)
- [Quick reference](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#reference)

 Overview

ElevateOS connects each building to RealPage OneSite. RealPage stays the place where residents, units and leases are maintained. ElevateOS reads that information on a schedule. Maintenance requests flow both ways. Pet and vehicle details that residents enter in a checklist are written back to RealPage.

Setup is light. ElevateOS needs two numbers from you: your **PMC ID** and the **Property ID (Site ID)** of each building. You do not give ElevateOS a RealPage username, password or API key.

### At a glance

| Function | Direction | How often | What it does |
| --- | --- | --- | --- |
| **Residents and households** | RealPage → ElevateOS | 6 AM, 9 AM, 12 PM, 3 PM and 6 PM Central Time | Creates and updates resident accounts, including household members who have their own email. Deactivates residents who no longer come back from RealPage. Read-only: nothing is sent back. |
| **Units and unit types** | RealPage → ElevateOS | Same schedule | Keeps units in step with RealPage and links residents to their units. Unit types come from RealPage floor plan descriptions. |
| **Leases** | RealPage → ElevateOS | Same schedule | Keeps lease dates and status in step with RealPage. Read-only. |
| **Work orders** | Both ways ⇄ | Sent to RealPage when submitted. Changes made in RealPage are checked every hour. | Requests created in ElevateOS are sent to RealPage. Requests created in RealPage appear in ElevateOS. Status and completion notes come back. From ElevateOS, only status goes to RealPage after the request is created. |
| **Pet and vehicle details** | ElevateOS → RealPage | When the resident completes the checklist task | Pet and vehicle forms completed in a checklist are added to the resident's RealPage record. |
| **Resident deactivation** | RealPage → ElevateOS | With each sync | Accounts of residents RealPage no longer returns, or marks as Former, are deactivated. They are not deleted. |
| **Rent payments and ledger** | Not supported | n/a | Pay Rent opens your own payment portal. See [Rent payments](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#payments). |

| **GOOD TO KNOW** RealPage is the source of truth for resident details. Change names, emails, units and move-out dates in RealPage. The next sync brings the change into ElevateOS. Edits made to those fields in ElevateOS are overwritten. |
| --- |

 Requirements

| **BEFORE YOU START** Your RealPage team must enable the integration for third-party vendors on the RealPage side. Confirm this with your RealPage representative before ElevateOS connects your building. ElevateOS cannot see or change anything inside your RealPage account. |
| --- |

### On the RealPage side

- **Your PMC ID.** This is the number RealPage uses for your property management company. It is the same for every site your company owns.
- **The Property ID (Site ID) of each building.** Use the active site. A cancelled or merged site stops working.
- **The integration enabled for third-party vendors.** Your RealPage team switches it on. RealPage has told ElevateOS customers there are no other settings to complete.
- **Service request lists set up in RealPage:** locations, issues and common areas, plus categories and problems if you use them. ElevateOS shows these lists in the request form. If a list is empty in RealPage, residents cannot finish a request.
- **Pet and vehicle type lists in RealPage**, if you will use the pet and vehicle checklist tasks.

No username, password or API key is needed from you.

### On the ElevateOS side

- **ElevateOS Support typically connects and tests the building.** Send your PMC ID and Property ID (Site ID) to your onboarding contact.
- To connect it yourself, **Places** appears in the **Dashboard** menu for Administrator and Manager roles. Property Manager accounts do not see it.
- Adding a new Property Management Company record needs an Administrator account.
- The building must already exist in ElevateOS.
- A building can be connected to one property management system at a time.

If you cannot see Places or a step is unavailable to your account, contact your ElevateOS representative.

### Resident data in RealPage

ElevateOS identifies each resident by email. These data rules decide whether a resident gets an account.

| Rule | Detail |
| --- | --- |
| **Email** | Residents without an email are skipped. Household members who have their own email get their own account. |
| **Names** | First name and last name must be present. A first name that contains an asterisk, such as some corporate lease entries, stops the account from activating. Remove the asterisk in RealPage. |
| **One person, one email** | Each email can belong to one resident profile. Duplicate emails in RealPage, including old Former profiles that use the same email, can block or mislink an account. A staff account that uses the same email also conflicts. |
| **Lease** | Residents on a current lease get active accounts. See below for applicants. |
| **Applicants** | Applicants are not synced by default. Applicants who have signed a lease come through as future residents when their screening result is approved. ElevateOS can include a wider set of applicants for a building on request. |
| **Phone numbers** | A phone number from RealPage is only filled in when the ElevateOS profile has none. Existing numbers are never overwritten. A phone field with no digits, such as N/A, can stop residents from syncing. Clear it in RealPage. |
| **Unit and building details** | Keep the unit number clean, and keep the building number and floor in their own fields. Spreadsheets of floors or building numbers uploaded to ElevateOS are overwritten by the next sync. |

| **RESIDENT ON NOTICE OR MONTH TO MONTH?** ElevateOS recognises residents on a current lease. If a resident who is on notice, month to month or about to move in is deactivated when they should not be, contact ElevateOS Support with their email and unit. |
| --- |

 Initial setup

Setup has three parts. Gather the two IDs, connect the building, then wait for the first sync and check the result.

### Gather your RealPage information

| You need | Used for |
| --- | --- |
| **PMC ID** | The **PMC ID** field of the company record |
| **A name for your own reference** | The **Name (Internal)** field |
| **Property ID (Site ID) of each building** | The **Property ID (Site ID)** field |

### Connect the building

ElevateOS Support can do this for you. To do it yourself as an Administrator or Manager:

1. **Confirm the RealPage side is ready.** Your RealPage team has enabled the integration for third-party vendors and the site is active.
2. **Open the building.** Go to **Dashboard \> Places**, then select the building from the list.
3. **Open the Integration tab.** Find the **Property Management System** section.
4. **Choose the integration type.** Set **Integration Type** to **RealPage**.
5. **Choose or add the management company.** If your company is already listed, pick it in **Property Management Company**. Otherwise click **Add New Property Management Company** (needs an Administrator account) and enter: 
     - **Name (Internal):** a name for your own reference.
     - **PMC ID:** your RealPage PMC ID.
    Both fields are required. The **Add New Company** button stays unavailable until each one is filled in. On success you see *New Property Management Company was successfully added.* and the company is selected for you. If your PMC ID is already on file you see an error. Pick the existing company from the dropdown instead.
6. **Enter the Property ID (Site ID).** Type the building's Site ID in **Property ID (Site ID)**. This is a free-text box. ElevateOS does not check the number against RealPage, so read it back twice. A typo is saved as if it were correct.
7. **Save.** Click **Save**, then reload the page. The button should now read **Connected with Real Page**. The message *Changes saved successfully.* can appear even when the save failed, so use the reload to confirm the building is connected.

| **GOOD TO KNOW** - Both the company and the Site ID must be set for the building to count as connected. Once connected, the type, company and Site ID fields are locked. The only way to change them is **Disconnect**. Read [Changing your connection](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#changes) first. - A company record cannot be edited after it is saved. If the PMC ID was entered wrongly, contact ElevateOS Support. - Several buildings that share a PMC ID use the same company record. Each building has its own Site ID. |
| --- |

### First sync

Connecting a building does not start a sync. The building is included in the next scheduled sync (see [Sync schedule](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#sync)). If you need the first sync sooner, ask ElevateOS Support to run one. There is no sync button in the dashboard.

### Verify the setup

1. The building shows **Connected with Real Page** after a page reload.
2. After the next sync window, a resident you know is on a current lease in RealPage appears in **Clients**, and their profile shows a **RealPage ID**.
3. Create a test maintenance request for a test unit. Check that it appears in RealPage. There is no RealPage work order number in ElevateOS, so search RealPage by resident, unit, description and date.
4. Change the status of the test request in ElevateOS and confirm RealPage shows the new status.
5. If you use a Pay Rent link, open it as a resident and confirm it lands on the right portal.

 Sync schedule

| What | When |
| --- | --- |
| **Residents, units and leases** | 6 AM, 9 AM, 12 PM, 3 PM and 6 PM Central Time |
| **Work orders created or changed in RealPage** | Checked every hour |
| **Work orders created in ElevateOS** | Sent to RealPage when the request is submitted |
| **Status changes made in ElevateOS** | Sent to RealPage when you save the change |
| **Pet and vehicle details** | When the resident completes the checklist task |

| **GOOD TO KNOW** - Resident sync is not real time. A move-in added in RealPage at 9:10 AM Central appears at the 12 PM sync. - If a sync fails for a building, the next scheduled run tries again. - The dashboard has no sync button, sync log or last-synced time. If you need a building synced sooner, or want to know how its last sync went, ask ElevateOS Support. - Dates arrive from RealPage in UTC and ElevateOS shows them in the building's time zone, so a move-in date can look one day early. |
| --- |

 Residents and accounts

### How residents get accounts

You do not enter residents in ElevateOS. At each sync, a resident who is valid in RealPage and has no ElevateOS account gets one. Household members with their own email get their own accounts.

Only residents found in RealPage stay active. A resident added by hand in the dashboard, or one who registers in the app, is deactivated at the next sync if they are not in RealPage. If you need test or demo accounts, create them in RealPage first.

### What stays up to date

Name, unit, address, floor, building number and move-out date are refreshed from RealPage at each sync. Lease dates and unit type come with them. Manual edits or uploads of those fields in ElevateOS are overwritten. Phone number is the exception. It is filled in only when the ElevateOS profile has none.

Each resident's profile shows a read-only **RealPage ID**. A resident whose email changes in RealPage may get a new ElevateOS account, and the old one is deactivated. Tell ElevateOS Support before bulk email changes.

### Move-outs and deactivation

ElevateOS deactivates a resident when RealPage marks them Former or no longer returns them. Deactivated accounts are not deleted. If the resident comes back in RealPage on a current lease, the next sync reactivates the account.

- Make move-out and status changes in RealPage. Deactivating or reactivating only in ElevateOS does not hold, because the next sync follows RealPage.
- Residents with a **RealPage ID** cannot delete their own account. They are asked to contact their administrator.
- Support can mark a corporate, model or test account as **Not Applicable** so sync leaves it alone. These accounts cannot submit maintenance requests.
- A resident who lived in another ElevateOS building has an account there. Support moves it to the new building. Sync does not.

| **BEFORE CHANGING A SITE ID OR MERGING PROPERTIES** If ElevateOS receives an empty resident list from RealPage, it deactivates every resident in that building. A wrong Site ID, a cancelled site or a merged property can cause this at the next sync. Tell ElevateOS before you change Site IDs or merge properties. |
| --- |

 Maintenance and work orders

### Lifecycle

1. **A resident or staff member submits a request.** In the app or in the dashboard. Roles that can create and view requests in the dashboard are Administrator, Manager, Property Manager, Staff and Shift Manager.
2. **ElevateOS sends it to RealPage.** The request is created in ElevateOS only if RealPage accepts it. If it does not, the dashboard shows *Cannot create a Maintenance Request. Please try again.* A resident who was just added in RealPage may need to wait for the next resident sync before a request for their unit works.
3. **Status and notes come back.** Requests created in RealPage appear in ElevateOS. RealPage status changes and completion notes are picked up on the hourly check. Status changes you save in ElevateOS go to RealPage right away.

### Finding a request in RealPage

ElevateOS does not show a RealPage work order number. In RealPage, search by the resident, unit, description and date. The resident's name is the contact name on the RealPage request, shortened to 30 characters.

### The request form

The RealPage form is different from the form for other systems. Lists come from your RealPage setup. There is no priority, short description, photo upload or phase.

#### Dashboard

| Field | Required | Notes |
| --- | --- | --- |
| **Select Request Type** | Yes | Unit or Common Area. A unit request needs a resident or unit. |
| **Request Description** | Yes | 250 characters maximum. |
| **Category, Problem and Issue** | No | Problem appears after Category, and Issue after Problem. Lists come from RealPage. |
| **Location Type** | Yes | Unit or Common Area. |
| **Common Area** | Yes, for a common area | List comes from RealPage. |
| **Location** | Yes | List comes from RealPage. |
| **Pets and Permission to Enter** | No | Permission to Enter is on by default. |
| **Entry Note** | No | 240 characters maximum. |

#### Mobile app

Residents and staff work through the same steps, in this order: location type, common area (for a common area), category, problem, issue, issue location, description, permission to enter and pets. The problem step is hidden when the category is Plumbing. A resident with a RealPage ID goes straight to the request form when opening the Maintenance tab.

### What is sent to RealPage

| When | What goes to RealPage |
| --- | --- |
| **Request is created** | Location, issue, contact name (first and last name, shortened to 30 characters), description and permission to enter, with the resident's contact details and unit. |
| **Request is updated** | Status only. |

Not sent to RealPage: photos, notes, priority, cancellation reason and assignee. Pets and Entry Note are kept in ElevateOS. Changes to location or issue made after creation stay in ElevateOS.

| **SPECIAL CHARACTERS** RealPage does not support special characters. An apostrophe or accented letter in a description can show as a question mark in RealPage. Use plain text for anything the RealPage team needs to read. |
| --- |

### What comes back from RealPage

| RealPage status | Shown in ElevateOS as |
| --- | --- |
| **In progress** | Pending |
| **On hold** | On Hold |
| **Complete** | Finished |
| **Any other status** | Shown as RealPage names it |

- **Completion notes** entered in RealPage appear as the **Job Summary** in ElevateOS. Long notes are shortened.
- Only status and job summary update after a request is imported. Later changes in RealPage to category, priority, description or assignee do not come across.
- RealPage requests are imported when they were created in about the last 3 months and changed in the last 7 days. Older requests are not imported.
- RealPage requests without a contact email are skipped.
- If RealPage reports a request is already completed, ElevateOS marks it Finished.

### Status changes and cancelling in ElevateOS

- Saving a new status in ElevateOS sends it to RealPage. If RealPage rejects the change, ElevateOS shows an error and the change is not made.
- Cancelling asks for a **Cancellation Reason** typed in ElevateOS. The reason stays in ElevateOS. RealPage receives only the Canceled status. Confirm in RealPage that the request shows as cancelled.
- The Priority column and filter in the dashboard list can appear for a RealPage building. They stay empty because RealPage requests have no priority.

 Checklists, inspections, pets and vehicles

### Pet and vehicle forms

On a RealPage-connected building, custom checklist tasks offer two data input types: **RealPage Pet** and **RealPage Vehicle**. Each can be added once per task. Administrator, Manager and Property Manager roles manage checklists.

1. **Open the task.** Create or edit a custom task in Checklists.
2. **Choose the data input type.** Select **RealPage Pet** or **RealPage Vehicle**.
3. **Review the form.** Click **Form structure** to see the fields. The form is fixed and cannot be changed. The input is always required, and it shows *Syncing w/ RealPage*.
4. **Save.** When a resident completes the task, ElevateOS adds the details to their RealPage record.

| Form | Fields |
| --- | --- |
| **RealPage Pet** | Pet Name, Breed, Age, Color, Weight, Pet Rent (Yes or No, required), Notes. |
| **RealPage Vehicle** | Model Year (required, 4 digits), Make, Model, License Plate Number, Color, State Code, Parking Assignment, Notes. |

- The resident must have a RealPage ID and a lease in RealPage.
- Each completion creates a new pet or vehicle record in RealPage. It never updates an existing one, so completing the task twice can create duplicates.
- Staff are not shown an error if RealPage rejects a value. Ask ElevateOS Support to check.
- Other completed checklists are not sent to RealPage.

### Inspection templates and unit types

In Checklists settings, the inspections tab shows **Integrated with Real Page** for connected buildings. Unit types come from the floor plan descriptions in RealPage. When you activate a template, ElevateOS asks you to match its unit types with your RealPage types. Move-in checklists are assigned by unit type.

- If a floor plan is missing from the list, check that it has a description in RealPage.
- Residents created in RealPage on the move-in day itself can miss a move-in checklist that is assigned a few days earlier.
- Inspection results are not sent to RealPage.

 Rent payments

ElevateOS does not read rent balances or post payments for RealPage. There is no ledger in the app for a RealPage building. The in-app payment flow is not available.

If your building has a **Pay Rent** link, residents are sent to your OneSite resident portal or your own payment provider's portal. ElevateOS onboarding sets up the link for each building. Payments made there are outside ElevateOS and are not affected by your RealPage connection. For balances and payment questions, residents contact your property team or the portal provider.

 Changing your connection

| **BEFORE YOU CHANGE ANYTHING** Tell ElevateOS before any change in RealPage that affects the connection: a new Site ID, a merged property, a new PMC ID or a move to another system. Do not wait until after the change. |
| --- |

### Disconnecting a building

1. Go to **Dashboard \> Places**, select the building and open the **Integration** tab.
2. Click **Disconnect** and confirm in **Disconnect from PMS**.

Disconnecting removes the RealPage link from the building's residents and clears its units in ElevateOS. Resident accounts are not deleted. The building no longer sends requests to RealPage. Contact ElevateOS before disconnecting a building that is in use.

### New Site ID, merged properties or a new PMC ID

- Get the new Site ID from your RealPage team. The PMC ID is usually the same. Send both to ElevateOS and Support updates the connection.
- A cancelled or merged Site ID stops working. RealPage reports the ID as no longer valid, and ElevateOS cannot sync until the building has a valid one.
- History from the old site, such as old work orders, does not move to the new site.
- Plan the change with ElevateOS so residents are not deactivated by an empty or wrong feed.

### Switching from RealPage to another system

Tell ElevateOS before the cutover. Work orders that were created while the building was on RealPage can no longer be completed or cancelled after the switch. ElevateOS will plan the order of steps with you.

 Troubleshooting

| **WHAT THE DASHBOARD DOES NOT SHOW** The ElevateOS dashboard has no sync log, no last-synced time, no sync button and no connection test. It does not show why a particular resident or work order was skipped. ElevateOS Support can check sync status for a building. See [What to send ElevateOS Support](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#support-checklist). |
| --- |

### The dashboard says "saved" but the building is not connected

Reload the page. If the button does not read **Connected with Real Page**, the save did not go through. Try again, or contact ElevateOS.

### "The provided ID is no longer valid"

- The Site ID was cancelled or merged in RealPage.
- Get the new Site ID from your RealPage team. The PMC ID is usually the same.
- Send both to ElevateOS Support.

### A resident does not appear in ElevateOS

- Wait for the next sync window.
- In RealPage, check the resident has an email, a first and last name without an asterisk, a move-in date and a current lease. Applicants are not synced by default.
- Check that no other RealPage profile, including an old Former one, uses the same email.
- Check the resident's phone field does not contain text with no digits.
- Check the building shows **Connected with Real Page** and the Site ID is correct.
- Send ElevateOS Support the resident email and unit.

### A resident was created, then deactivated

- Only residents found in RealPage stay active. Check whether the resident was added by hand or registered in the app and has no matching RealPage profile with the same email.
- Check the resident is not marked Former in RealPage and has no past move-out date.
- If several residents were deactivated at once, check whether the Site ID changed or the property was merged. Contact ElevateOS right away.

### A resident on notice or month to month was deactivated

ElevateOS recognises residents on a current lease. Contact ElevateOS Support with the resident's email and unit, and we will check how their lease comes through.

### A resident shows in the wrong building or says the account already exists

A resident who lived at another ElevateOS building keeps the account there. Contact ElevateOS Support to move it. Sync does not move accounts between buildings.

### A phone number, name, unit or floor is wrong or not updating

- Name, unit, address, floor, building number and move-out date come from RealPage. Fix them in RealPage.
- A phone number is only filled in when the ElevateOS profile has none. Residents can update their own number in the app.

### A work order is missing in RealPage

- A request is created in ElevateOS only if RealPage accepted it. If you saw an error, it was not created.
- Search RealPage by resident, unit, description and date. ElevateOS shows no RealPage number.
- Check the request has a location and an issue selected, and that the resident has a contact email.
- Allow up to an hour for changes to appear in both directions.

### A work order is missing in ElevateOS

- Requests created in RealPage are checked every hour.
- The request needs a contact email in RealPage. Without one it is skipped.
- Requests created more than about 3 months ago are not imported.
- Send ElevateOS Support the resident, unit, description and the date it was created in RealPage.

### A work order status does not match

- RealPage changes arrive on the hourly check. Wait for it before comparing.
- RealPage In progress shows as Pending in ElevateOS.
- Only status goes from ElevateOS to RealPage after creation. Notes, priority, assignee and cancellation reason stay where they were entered.
- Send ElevateOS Support the resident, unit, description and both statuses.

### Special characters show as question marks in RealPage

RealPage does not support special characters. Apostrophes and accented letters can appear as question marks. Use plain text.

### A resident cannot invite a guest

Guest invites can be blocked when the resident's lease end or move-out date in RealPage is in the past, for example on a month-to-month lease. Update the date in RealPage, or contact ElevateOS Support.

### A move-in checklist was not assigned

- Check the unit type is matched to a RealPage floor plan in Checklists settings.
- Check the resident was created in RealPage a few days before the move-in date. A resident added on the move-in day can miss the assignment.

### A pet or vehicle did not reach RealPage

- Check the resident has a RealPage ID and a lease, and the required fields were filled in.
- Staff are not shown an error for this. Ask ElevateOS Support to check.

### We are switching from RealPage to another system

Tell ElevateOS before the cutover. See [Changing your connection](https://help.elevateos.com/how-does-the-elevated-living-onesite-/-realpage-integration-work#changes).

### What to send ElevateOS Support

- Building name
- PMC ID and Property ID (Site ID)
- Resident email and unit (for resident issues)
- For maintenance issues, the resident, unit, description and date, plus the ElevateOS request ID
- The date and time it happened, with time zone
- A screenshot of what you see, and of the profile in RealPage if you can
- What you already checked in RealPage

*You never need to send a password.*

 FAQ

### Does ElevateOS need my RealPage username or password?

No. ElevateOS needs your PMC ID and the Property ID (Site ID) of each building. Your RealPage team must enable the integration for third-party vendors on the RealPage side.

### Who connects the building?

ElevateOS Support typically connects and tests it. Administrators and Managers can also do it in Places. Adding a new company record needs an Administrator.

### How often does ElevateOS sync with RealPage?

Residents, units and leases sync at 6 AM, 9 AM, 12 PM, 3 PM and 6 PM Central Time. Work orders from RealPage are checked every hour.

### Do I need to create residents in ElevateOS?

No. Add them in RealPage with an email. Accounts are created at the next sync.

### Can I edit a resident's name or unit in ElevateOS?

Those fields are refreshed from RealPage at every sync, so edits are overwritten. Change them in RealPage.

### When does a resident lose access at move-out?

At the next sync after RealPage marks them Former or stops returning them. Make move-out changes in RealPage.

### Can residents pay rent in the ElevateOS app?

Not for RealPage buildings. Pay Rent opens your own payment portal.

### Does ElevateOS provide RealPage technical support?

No. ElevateOS supports the ElevateOS side of the connection. Questions about RealPage settings, resident profiles and licensing go to RealPage or your RealPage administrator.

 What RealPage does and does not do in ElevateOS

| Feature | With RealPage | Notes |
| --- | --- | --- |
| **Residents, units and leases** | Yes, read-only | RealPage to ElevateOS, several times a day. |
| **Work orders** | Yes, both ways | Status and job summary come back. Status goes out after creation. |
| **Pet and vehicle details** | Yes, from checklists | Always adds a new record. |
| **Rent payments, balances and ledger** | No | Pay Rent is a link to your own portal. |
| **Other completed checklists and inspection results** | No | Unit types are used to match move-in inspections. |
| **Vehicle import from RealPage** | No | Vehicles are only written to RealPage. |
| **Custom field mapping** | No | — |
| **Work order photos and attachments** | No | — |
| **Notes, priority, cancellation reason and assignee on work orders** | No | These stay in ElevateOS. |
| **Rent amounts and deposits on leases** | No | Lease dates and status do sync. |
| **Applicants** | Limited | Lease-signed, approved applicants only, unless ElevateOS enables more for the building. |
| **Sync log, sync button and connection test in the dashboard** | No | Ask ElevateOS Support. |

Other property management systems that ElevateOS supports may cover more. If a feature you need is missing here, ask your ElevateOS representative.

 Quick reference

### Glossary

| Term | Meaning |
| --- | --- |
| **PMC ID** | The number RealPage uses for your property management company. You enter it once when you add the company in ElevateOS. |
| **Site ID** | The number RealPage uses for one property. You enter it as **Property ID (Site ID)**. ElevateOS does not check it against RealPage. |
| **OneSite** | RealPage's property management system. Residents, units, leases and service requests live here. |
| **Unit type** | The floor plan description from RealPage. ElevateOS uses it to match move-in inspections. |
| **RealPage ID** | Shown on a resident profile. It identifies the resident in RealPage. |
| **Management company record** | The saved name and PMC ID for your company in ElevateOS. |
| **Not Applicable** | A status Support can set so sync leaves an account alone, for corporate, model or test accounts. |

### Setup checklist

#### In RealPage

- ☐ Confirmed with your RealPage representative that the integration is enabled for third-party vendors
- ☐ PMC ID and Property ID (Site ID) collected, and the site is active
- ☐ Service request locations, issues and common areas set up
- ☐ Resident emails, names and move-in and move-out dates checked

#### In ElevateOS

- ☐ IDs sent to ElevateOS Support, or entered in Places
- ☐ Integration Type set to RealPage, company chosen, Site ID typed and double-checked, Save clicked
- ☐ Page reloaded and button reads Connected with Real Page
- ☐ Pay Rent link set up by onboarding, if you use one

#### After the first sync

- ☐ A known resident on a current lease appears with a RealPage ID
- ☐ A test work order reaches RealPage and a status change carries across

*For questions about your setup, contact your ElevateOS representative or ElevateOS Support.*

- [Getting started](https://help.elevateos.com/getting-started?hsLang=en)
- [Integrations](https://help.elevateos.com/integrations?hsLang=en#main-content)

    - [Access Control - 2N](https://help.elevateos.com/integrations?hsLang=en#access-control-2n)
    - [Access Control - Brivo](https://help.elevateos.com/integrations?hsLang=en#access-control-brivo)
    - [Access Control - ButterflyMX](https://help.elevateos.com/integrations?hsLang=en#access-control-butterflymx)
    - [Access Control - iGloo](https://help.elevateos.com/integrations?hsLang=en#access-control-igloo)
    - [Access Control - Latch](https://help.elevateos.com/integrations?hsLang=en#access-control-latch)
    - [Access Control - OpenPath](https://help.elevateos.com/integrations?hsLang=en#access-control-openpath)
    - [Access Control - PointCentral](https://help.elevateos.com/integrations?hsLang=en#access-control-pointcentral)
    - [Access Control - Rently](https://help.elevateos.com/integrations?hsLang=en#access-control-rently)
    - [Access Control - Salto KS](https://help.elevateos.com/integrations?hsLang=en#access-control-salto-ks)
    - [Access Control - SALTO Space](https://help.elevateos.com/integrations?hsLang=en#access-control-salto-space)
    - [Access Control - Schlage](https://help.elevateos.com/integrations?hsLang=en#access-control-schlage)
    - [Access Control - Swiftlane](https://help.elevateos.com/integrations?hsLang=en#access-control-swiftlane)
    - [Package Lockers - Luxer One](https://help.elevateos.com/integrations?hsLang=en#package-lockers-luxer-one)
    - [Package Lockers - Parcel Pending](https://help.elevateos.com/integrations?hsLang=en#package-lockers-parcel-pending)
    - [PMS - Entrata](https://help.elevateos.com/integrations?hsLang=en#pms-entrata)
    - [PMS - Onesite / Realpage](https://help.elevateos.com/integrations?hsLang=en#pms-onesite-realpage)
    - [PMS - Resman](https://help.elevateos.com/integrations?hsLang=en#pms-resman)
    - [PMS - Yardi](https://help.elevateos.com/integrations?hsLang=en#pms-yardi)
- [Management Portal](https://help.elevateos.com/management-portal?hsLang=en#main-content)

    - [Dashboard](https://help.elevateos.com/management-portal?hsLang=en#dashboard)
    - [Calendar](https://help.elevateos.com/management-portal?hsLang=en#calendar)
    - [Contacts](https://help.elevateos.com/management-portal?hsLang=en#contacts)
    - [Marketing - Announcements & Surveys](https://help.elevateos.com/management-portal?hsLang=en#marketing-announcements-surveys)
    - [Marketing - Community Feed & Interest Groups](https://help.elevateos.com/management-portal?hsLang=en#marketing-community-feed-interest-groups)
    - [Marketing - Gift Cards](https://help.elevateos.com/management-portal?hsLang=en#marketing-gift-cards)
    - [Marketing - Rewards](https://help.elevateos.com/management-portal?hsLang=en#marketing-rewards)
    - [Marketing - Digital Signage](https://help.elevateos.com/management-portal?hsLang=en#marketing-digital-signage)
    - [Marketing - Reputation Management](https://help.elevateos.com/management-portal?hsLang=en#marketing-reputation-management)
    - [Marketing - Digital Displays](https://help.elevateos.com/management-portal?hsLang=en#marketing-digital-displays)
    - [Operations - Checklists](https://help.elevateos.com/management-portal?hsLang=en#operations-checklists)
    - [Operations - User Management](https://help.elevateos.com/management-portal?hsLang=en#operations-user-management)
    - [Operations - Amenities & Reservations](https://help.elevateos.com/management-portal?hsLang=en#operations-amenities-reservations)
    - [Operations - Maintenance](https://help.elevateos.com/management-portal?hsLang=en#operations-maintenance)
    - [Operations - Visitors](https://help.elevateos.com/management-portal?hsLang=en#operations-visitors)
    - [Operations - Packages](https://help.elevateos.com/management-portal?hsLang=en#operations-packages)
    - [Operations - Package Room](https://help.elevateos.com/management-portal?hsLang=en#operations-package-room)
    - [Operations - Shift & Action Log](https://help.elevateos.com/management-portal?hsLang=en#operations-shift-action-log)
    - [Operations - Community Essentials](https://help.elevateos.com/management-portal?hsLang=en#operations-community-essentials)
    - [Operations - Parking Management](https://help.elevateos.com/management-portal?hsLang=en#operations-parking-management)
    - [Operations - Valet CRM](https://help.elevateos.com/management-portal?hsLang=en#operations-valet-crm)
    - [Unified Inbox](https://help.elevateos.com/management-portal?hsLang=en#unified-inbox)
    - [Operations - Internal Inspections](https://help.elevateos.com/management-portal?hsLang=en#operations-internal-inspections)
    - [Operations - Escalations](https://help.elevateos.com/management-portal?hsLang=en#operations-escalations)
- [Front Desk & Concierge](https://help.elevateos.com/front-desk-concierge?hsLang=en#main-content)

    - [Getting Started](https://help.elevateos.com/front-desk-concierge?hsLang=en#getting-started)
    - [Packages](https://help.elevateos.com/front-desk-concierge?hsLang=en#packages)
    - [Shift & Action Log](https://help.elevateos.com/front-desk-concierge?hsLang=en#shift-action-log)
    - [Market Shop](https://help.elevateos.com/front-desk-concierge?hsLang=en#market-shop)
- [Resident App](https://help.elevateos.com/resident-app?hsLang=en#main-content)

    - [Getting Started](https://help.elevateos.com/resident-app?hsLang=en#getting-started)
    - [Engage - Neighborhood Perks](https://help.elevateos.com/resident-app?hsLang=en#engage-neighborhood-perks)
    - [Operate - Reservable Amenities](https://help.elevateos.com/resident-app?hsLang=en#operate-reservable-amenities)
    - [Operate - Maintenance](https://help.elevateos.com/resident-app?hsLang=en#operate-maintenance)
- [Portfolio Management](https://help.elevateos.com/portfolio-management?hsLang=en#main-content)

    - [Getting Started](https://help.elevateos.com/portfolio-management?hsLang=en#getting-started)

- [Default HubSpot Blog](http://blog.elevatedliving.com/blog)

[![Elevate OS Logo (2)](https://help.elevateos.com/hs-fs/hubfs/REBRAND/Elevate%20OS%20Logo%20(2).png?width=200&height=133&name=Elevate%20OS%20Logo%20(2).png "Elevate OS Logo (2)")](http://elevatedliving.com)

Help Center

Copyright © 2026, ElevateOS