> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.propexo.com/onboarding/10-performing-your-first-syncs-in-propexo/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.propexo.com/_mcp/server.

# Performing your First Syncs in Propexo

**Syncs** keep your Propexo integration up to date with the latest data from your PMS.

* Regular syncs only look back a limited amount of time to reduce record processing and avoid unnecessary API usage, which factors into your subscription cost.
* If you need to pull in older records, you can run a **backsync** to load historical data.

---

## Enabling an Integration

By default, new integrations start in a **disabled state**. This ensures all necessary data access is in place before syncing begins.

To activate your integration:

1. Open the menu in the top-right corner of the page (three dots).
2. Click **Enable**.

![enable integration](/_fern-files/propexo.docs.buildwithfern.com/4178eae9382eb4a3a7e8d50bf1c8f703c51039e81921919f85e2e15ef95e8668/docs/assets/onboarding-screenshots/enable-int.gif)

---

## First Sync

Once your integration is enabled, Propexo will begin its **first sync** with your PMS.

* **Small dataset**: as little as 60 seconds.
* **Large dataset**: up to several hours.

During this process, you may need to **refresh the page** to view updated results.

---

## Backsyncing

A **backsync** loads all historical data from your PMS into Propexo.

* Useful if you need a **complete dataset** beyond what regular syncs provide.
* Recommended upon **initial integration setup**.

To perform a backsync:

1. Click the **Sync Now** button on your integration view.\
   ![SyncNow](/_fern-img/9f784a9b8cd55c1033c288acf0835596c8b25170b3b91c2b652717c139923826.webp)
2. Select **Back-Sync**.
   ![SyncNow](/_fern-img/098fce8fce34de8c400990ace99d5332302fea5ac8cc8299ccef06cc7f5e50e6.webp)
3. Choose to backsync all models, or select which models to backsync. For a new integration, it is highly recommended that all models be synced.\
   ![SyncNow](/_fern-img/244f93ac74b7718100ac1595c5dd9463c0bfc2ad486a02b335c2d4770b2afb97.webp)
4. Click **Start Sync**.

---

## Manual Syncs via the Propexo API

You can also trigger syncs directly through **Propexo's API**:

* **Manual Sync**: [Trigger a Manual Sync](https://docs.propexo.com/api-reference/configuration-ap-is/admin/trigger-a-manual-sync-on-an-integration)
* **Backsync**: [Trigger a Backsync](https://docs.propexo.com/api-reference/configuration-ap-is/admin/trigger-a-backsync-on-an-integration)

When making these requests, you can specify which **models** to include in the sync.

This allows you to:

* Limit the scope of the operation.
* Reduce processing.
* Speed up sync times.