# How to Pull Property Data from Reapit Using Power Reports

This guide explains how to export comprehensive property data from Reapit using Power Reports. This export is essential for **valuations attribution analysis** - helping you understand which lead sources (including SalesRook) deliver the most valuable instructions and completions.

#### Why Export This Data?

By exporting your Reapit property data with key date fields (Created, Instructed, Exchange/Tenancy Start), you can:

* **Track which sources generate instructions** - Compare performance across Company Website, SalesRook, Rightmove, Zoopla, OnTheMarket
* **Measure conversion rates** - See which channels turn enquiries into actual instructions
* **Prove ROI** - Demonstrate the value of your marketing spend and technology investments
* **Optimize your strategy** - Make data-driven decisions about portal spending

The SalesRook team uses this data to create comprehensive attribution reports showing exactly where your most valuable instructions originate.

**Time Required:** 5-10 minutes\
**Difficulty:** Beginner\
**Applies to:** All Reapit users working with SalesRook

***

### What You'll Export

Using this method, you can export detailed property information including:

* Property references and office assignments
* Complete address details (house number, name, postcode)
* Current status (Sales and Lettings)
* Primary contact information and email addresses
* Last modified dates
* And many other custom fields

***

### Step-by-Step Instructions

#### Step 1: Access Power Reports

1. In Reapit, navigate to **Reports** in the main menu
2. Select **Power Reports**

<div data-with-frame="true"><figure><img src="/files/kv3JfyoZjrU33yLGTDe9" alt=""><figcaption></figcaption></figure></div>

***

#### Step 2: Select Property Report Type

1. Choose **Property Report** from the available report types
2. **Important:** Check the box to **include archived records**
   * This ensures you capture all historical property data

<div data-with-frame="true"><figure><img src="/files/6F02PWceeuWOhjIgziXm" alt=""><figcaption></figcaption></figure></div>

***

#### Step 3: Run Separate Reports for Sales and Lettings

⚠️ **Note:** You'll need to run this process twice - once for Sales and once for Lettings

**For Sales:**

* Select the Sales department/type

**For Lettings:**

* Select the Lettings department/type

<div data-with-frame="true"><figure><img src="/files/CAknSlQNBpx88STycW6y" alt=""><figcaption></figcaption></figure></div>

***

#### Step 4: Add Search Criteria

At least one search criterion must be added to run the report. We recommend:

1. Add criterion: **Registered date**
2. Set it to: **before \[future date]**
   * Example: "Registered before 31/12/2026"
   * This captures all records in your system

<div data-with-frame="true"><figure><img src="/files/WQBc7HENPUaeN2BnEy5X" alt=""><figcaption></figcaption></figure></div>

***

#### Step 5: View the Results Grid

Once the report runs, you'll see a grid displaying all matching records with various fields showing.

<div data-with-frame="true"><figure><img src="/files/1z0KJsO4N0uhsBvWjk1S" alt=""><figcaption></figcaption></figure></div>

***

#### Step 6: Create a Custom Excel Template

1. **Right-click** on any column header
2. Hover over **Export to**
3. Select **Create/Edit Custom Excel Template**

<div data-with-frame="true"><figure><img src="/files/Kgr5UUuNBlo8jmh7jieH" alt=""><figcaption></figcaption></figure></div>

***

#### Step 7: Choose Template Type

You have two options:

* **Create from Blank:** Start with no fields pre-selected
* **Create from Standard:** Includes the fields currently visible in the grid

**Recommendation:** Choose "Create from Standard" to start with existing fields, then add more.

<div data-with-frame="true"><figure><img src="/files/IcoMdFM2UIqcSV9vmrZW" alt=""><figcaption></figcaption></figure></div>

***

#### Step 8: Add Custom Fields

1. Click the **Add** button at the bottom of the template editor

<div data-with-frame="true"><figure><img src="/files/a7DIfRauYJrEqWo0UQEg" alt=""><figcaption></figcaption></figure></div>

2. For each field you want to include, you'll need:

* **Header:** The column name that will appear in Excel
* **Merge Code:** The C# string that points to the database object e.g. `Property.Code`&#x20;

<div data-with-frame="true"><figure><img src="/files/kNksX31Ibd2D3GdCwNrO" alt=""><figcaption></figcaption></figure></div>

***

### Essential Merge Codes for Valuations Analysis

Here are the most useful merge codes for property analysis:

| Field                              | Merge Code                                |
| ---------------------------------- | ----------------------------------------- |
| Reference                          | `Property.Code`                           |
| Office Name                        | `Property.ActiveOffName`                  |
| House Number                       | `Property.Address.HseNo`                  |
| House Name                         | `Property.Address.HseName`                |
| Address Line 1                     | `Property.Address.Address1`               |
| Address Line 2                     | `Property.Address.Address2`               |
| Address Line 3                     | `Property.Address.Address3`               |
| Address Line 4                     | `Property.Address.Address4`               |
| Postcode                           | `Property.Address.Postcode`               |
| Status (Sales)                     | `Property.Sales.StatusNameGrid`           |
| Status (Lettings)                  | `Property.Lettings.StatusNameGrid`        |
| Primary Contact                    | `Property.CurrentCntName`                 |
| Primary Contact Email              | `Property.PrimaryContact.GetPhone("e")`   |
| Primary Contact Mobile             | `Property.PrimaryContact.GetPhone("sms")` |
| Created Date                       | `Property.Created`                        |
| Instructed Date                    | `Property.Sales.Instructed`               |
| Exchange Date (Sales)              | `Property.Sales.Exchange`                 |
| Last Tenancy Start Date (Lettings) | `Property.Lettings.LastTenancyStart`      |
| Last Modified Date                 | `Property.Amend`                          |

#### How to Add Each Field

1. Click **Add**
2. Enter the **Header** name (e.g., "Postcode")
3. Enter the corresponding **Merge Code** (e.g., `Property.Address.Postcode`)
4. Repeat for each field you need

<div data-with-frame="true"><figure><img src="/files/nY5WudFaBmx5zXIImdVw" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}

#### 💡 Note on Merge Codes

Your merge codes may differ slightly depending on your Reapit database configuration and any customisations you've designed with Reapit.

**Need help finding the right merge code?**

* Click the blue **"Merge Code"** link in the Excel Export Column Edit dialog (shown above) to see available options for your database
* Contact your **Reapit Customer Success Manager** for support with custom fields or database-specific merge codes

The merge codes listed in this guide are standard for most Reapit configurations, but your setup may have additional custom fields or slightly different naming conventions.
{% endhint %}

***

#### Step 9: Save and Export the Template

1. Give your template a descriptive name
   * Example: "Property Export - Sales" or "Valuations Analysis Export"
2. Click **Accept**

<div data-with-frame="true"><figure><img src="/files/8y0S49vW5X2DcG0I5X8b" alt=""><figcaption></figcaption></figure></div>

***

#### Step 10: Confirm Export

When prompted "Export using this template?", click **Yes**

The report will export to Excel with all your selected fields.

<div data-with-frame="true"><figure><img src="/files/y3yHZHOLn7hJhWw92xqL" alt=""><figcaption></figcaption></figure></div>

***

### Using Your Template in Future

Once you've created a custom template, you can reuse it quickly:

1. Run your Power Report as normal (Steps 1-5)
2. **Right-click** on any column header
3. Select **Export to** > **Excel Spreadsheet (.xls) - Custom**
4. Find and select your previously created template

This saves significant time for recurring reports!

<div data-with-frame="true"><figure><img src="/files/RSQOHRHZxxFjhwHz21LS" alt=""><figcaption></figcaption></figure></div>

***

### Tips and Best Practices

#### For Valuations Analysis & SalesRook Attribution

When analysing valuations opportunities and measuring SalesRook's performance, include these fields:

* **All address fields** (especially Postcode - for matching with SalesRook data)
* **Status fields** (to identify current instruction status)
* **Created Date** (when the property first entered your system)
* **Instructed Date** (when you won the instruction - critical for conversion tracking)
* **Exchange Date** (for sales properties - measures final completion)
* **Last Tenancy Start Date** (for lettings properties - tracks successful lets)
* **Last Modified Date** (to prioritise recent activity)
* **Primary contact details** (to reach property owners)

These date fields enable SalesRook to create attribution reports showing:

* Which enquiry sources convert to instructions
* Time from initial enquiry to instruction
* Completion rates by source (exchanges/tenancy starts)
* Full journey tracking for ROI analysis

#### Naming Your Templates

Use clear, descriptive names like:

* "Sales Properties - Full Export"
* "Lettings Valuations Analysis"
* "Monthly Property Report"
* "SalesRook Attribution Export"

#### Running Regular Reports

Consider scheduling regular exports (e.g., quarterly) to:

* **Track SalesRook performance** over time with attribution analysis
* **Identify trending postcodes** and high-performing sources
* **Monitor instruction conversion rates** across different channels
* **Spot opportunities for follow-up** on stalled valuations
* **Justify marketing spend** with data-driven insights

**Pro tip:** Export data covering at least 6 months for meaningful trend analysis. Include properties modified/created during your analysis period to capture the complete picture.

***

### Troubleshooting

**Problem:** Report returns no results

* **Solution:** Check your search criteria aren't too restrictive. Use a future date for the "Registered before" filter.

**Problem:** Can't find a specific field

* **Solution:** Contact Reapit support for the correct merge code, or check Reapit's documentation.

**Problem:** Template doesn't save

* **Solution:** Ensure you've given it a unique name and have the necessary permissions.

***

### Integrating with SalesRook

Once you've exported your property data, you can work with the SalesRook team to create comprehensive **valuations attribution analysis**.

#### Why This Matters

Understanding which sources generate your most valuable instructions is critical for optimising your marketing spend and lead generation strategy. By exporting your Reapit property data, SalesRook can help you:

**Track Performance by Source**

* Identify which enquiry sources (Company Website, SalesRook, Rightmove, Zoopla, OnTheMarket) convert to instructions
* Compare conversion rates across different channels
* Measure which sources drive actual completions (sales/lettings)

**Measure SalesRook's Impact**

* Attribute valuations captured by your AI persona to actual instructions
* Track the full journey from initial enquiry to instruction to completion
* Calculate ROI on your SalesRook investment

**Optimise Your Strategy**

* Identify high-performing sources to increase investment
* Spot underperforming channels that need improvement
* Make data-driven decisions about portal spending

#### What SalesRook Does With Your Data

When you provide your Reapit property export, we:

1. **Match valuations to instructions** - Cross-reference postcodes and addresses from SalesRook-identified valuations with your actual property records
2. **Calculate conversion rates** - Determine how many SalesRook-captured leads became instructions vs other sources
3. **Track outcomes** - Monitor which instructions progressed to exchange/completion
4. **Create visual reports** - Deliver clear dashboards showing performance by source
5. **Provide actionable insights** - Highlight opportunities to improve conversion rates

#### Example Analysis

A typical SalesRook valuations analysis report includes:

* **Source comparison** - Properties, instructions, and completions by enquiry source
* **Tracked vs untracked** - Visibility into historical data before SalesRook implementation
* **League tables** - Performance rankings across all tracked sources
* **Conversion funnels** - Visual representation of enquiry → instruction → completion

This analysis helps you demonstrate the value of AI-powered lead qualification and justify continued investment in tools like SalesRook.

#### How to Share Your Data

1. Export your property data following this guide
2. Send the Excel files to your SalesRook account manager or <support@salesrook.com>
3. We'll typically deliver your analysis within 1-2 weeks

**Recommended export frequency:** Quarterly or bi-annually to track performance trends over time.

***

### Need Help?

If you have questions about:

* **Reapit Power Reports:** Contact Reapit support
* **Using this data with SalesRook:** Contact our support team at <support@salesrook.com>
* **Custom merge codes:** Reapit's documentation or support team can provide additional codes


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.salesrook.com/salesrook-core/how-to-pull-property-data-from-reapit-using-power-reports.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.