---
title: Understand Sensor Merges
description: When to merge sensors and understanding the merge (and replacement) processes.
---

[Skip to content](https://support.conserv.io/knowledge/understand-sensor-merges#main-content)

English

Show submenu for translations

[Contact us](https://support.conserv.io/knowledge/kb-tickets/new?hsLang=en)

[![Cnsrv\_wmM\_mix\_rgb - MEDIUM-1.png\]](https://support.conserv.io/hs-fs/hubfs/Cnsrv_wmM_mix_rgb%20-%20MEDIUM-1.png?height=40&name=Cnsrv_wmM_mix_rgb%20-%20MEDIUM-1.png)](https://conserv.io/)

- [Support](https://support.conserv.io/knowledge)
- [Blog](https://support.conserv.io/blog)

Open main navigation

Close main navigation

- [Support](https://support.conserv.io/knowledge)
- [Blog](https://support.conserv.io/blog)
- English
  
  Show submenu for translations
- [Contact us](https://support.conserv.io/knowledge/kb-tickets/new)
- [Contact Us](https://support.conserv.io/knowledge/kb-tickets/new)

[Contact Us](https://support.conserv.io/knowledge/kb-tickets/new?hsLang=en)

 How can we help you?

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

1. [Help center](https://support.conserv.io/knowledge?hsLang=en)
2. [Installation and Setup](https://support.conserv.io/knowledge/installation-and-setup?hsLang=en)
3. [Add, Move, Swap and Merge Sensors](https://support.conserv.io/knowledge/installation-and-setup?hsLang=en#add-move-swap-and-merge-sensors)

# Understand Sensor Merges

## When to merge sensors and understanding the merge process

**Table of Contents**

- [What Is a Sensor Merge?](https://support.conserv.io/knowledge/understand-sensor-merges#What-Is-a-Sensor-Merge)
- [When to Merge Sensors](https://support.conserv.io/knowledge/understand-sensor-merges#when-to-merge-sensors)
- [When Not to Merge Sensors](https://support.conserv.io/knowledge/understand-sensor-merges#when-not-to-merge-sensors)
- [Important Considerations Before Merging](https://support.conserv.io/knowledge/understand-sensor-merges#Important-Considerations-Before-Merging)
- [How to Merge Sensors](https://support.conserv.io/knowledge/understand-sensor-merges#How-to-Merge-Sensors)
- [After the Merge](https://support.conserv.io/knowledge/understand-sensor-merges#After-the-Merge)
- [Additional Resources](https://support.conserv.io/knowledge/understand-sensor-merges#Additional-Resources)<https://support.conserv.io/knowledge/understand-sensor-merges#Additional-resources>

### What Is a Sensor Merge?

A sensor merge takes the data from a new sensor and places it on top of an old sensor to maintain continuity of readings over time in spite of device changes. This process allows you to keep all historical data in one location while transitioning to new hardware.

When you complete a merge, the old sensor card gets moved to Inactive and "disappears" from the Active dashboard. The old sensor card can be brought back by clicking the **RESTORE SENSOR** button, but Conserv does not recommend this as it can create noise in the new sensor graph.

### When to Merge Sensors

You may want to merge sensor cards in the following situations:

- **Two imported sensors**: If you have two imported (non-Conserv) sensors whose data you want to join
- **New customer with historical data**: If you are a new customer with old imported sensor data and a brand new Conserv sensor, and want all the data for that location to be in the same place
- **Renewing customer**: If you are a renewing customer with an old Conserv Smart Collection Sensor (SCS) and a new SCS to replace it.

### When Not to Merge Sensors

Do not merge sensors in the following situations:

- **Different physical locations**: When the data does not actually reflect the readings of the same physical spot.
- **Moving sensor locations**: Merges should not be done as part of moving sensor locations without deep consideration, as this can cause many data issues. If you want to move sensor locations, see [Import Data When Moving Sensors](https://support.conserv.io/knowledge/import-data-when-moving-sensors?hsLang=en) or [contact the Support Team](https://support.conserv.io/knowledge/kb-tickets/new?hsLang=en) if you are unsure.

### Important Considerations Before Merging

**Warning: Merge Order**

Always merge sensors in the correct order. The **new** sensor must replace the **old.** At the time of writing this article (September 2025) merging sensors in the wrong order cannot be undone without an engineer's assistance.

**Helpful tip**

The serial number of the newer sensor will always be a bigger number than the old sensor (for example, c006500 is a newer sensor than c004200).

**Additional recommendations**:

- Do not attempt too many merges at the same time, as this can cause confusion and lead to errors merging sensors in the wrong order or merging the wrong sensors together.
- For customers with many sensors, Conserv recommends creating simple Excel tables of what old sensors next to their new replacements for future reference in case of mistakes.
- Merging requires attention to detail to avoid merging the wrong sensors or merging them in the wrong order. Conserv recommends setting aside time to perform merges with thoughtful consideration.

**Important**

 A merge will join the data from an old and a new sensor into the same graph.

Once the new sensor begins taking readings after activation, merge it as soon as possible to avoid a period of time in your graph when you will have live data from two sensors at the same time in the same graph.

**Conserv does not recommend starting merge procedures when you are pressed for time or activating new sensors and waiting a long time to perform the merge after the new sensor has been activated.**

### How to Merge Sensors

You can merge sensors using two methods:

- **Web browser dashboard method**: Available for all merge scenarios (imported sensors, new customers, and renewing customers).
- **Conserv Cloud Mobile App method**: Available for SCS renewals (renewing customers with old and new SCS units). The mobile method is more user-friendly and you are less likely to make a mistake with that method unless you scan the wrong sensors.

**Before you begin**: Ensure that your new sensor is [activated and reporting data](https://support.conserv.io/knowledge/place-mount-and-activate-sensors?hsLang=en#bring-scs-online) before proceeding with the merge.

For detailed step-by-step instructions, see the appropriate articles:

- [Merge Two Sensors Using Conserv Cloud Web Interface](https://support.conserv.io/knowledge/swap-and-merge-renewal-sensors?hsLang=en)<https://support.conserv.io/knowledge/swap-and-merge-renewal-sensors?hsLang=en>
- [Merge Two Sensors Using the Conserv Cloud Mobile App](https://support.conserv.io/knowledge/merge-two-sensors-using-the-mobile-app?hsLang=en)

### After the Merge

After completing the merge:

1. **Remove the old sensor**: Replace the old sensor with the new sensor in its physical location. Do not leave a lot of time between performing the merge and placing the new sensor in the correct physical location or you will be getting data from the wrong location.
2. **Verify data continuity**: Check that the new sensor is reporting data correctly in the merged sensor card
3. **Remove old sensor batteries**: Take out the batteries from the old sensor to prevent duplicate data reporting. For instructions on opening the sensor, see [Reset a Sensor](https://support.conserv.io/knowledge/reset-a-sensor?hsLang=en)

### Additional Resources

- - [Import Data When Moving Sensors](https://support.conserv.io/knowledge/import-data-when-moving-sensors?hsLang=en)
    - [Recover Deleted Sensor](https://support.conserv.io/knowledge/recover-deleted-sensor?hsLang=en)
    - [Place, Mount, and Activate Sensors](https://support.conserv.io/knowledge/place-mount-and-activate-sensors?hsLang=en)
    - [Contact the Support Team](https://support.conserv.io/knowledge/kb-tickets/new?hsLang=en)

- [Introduction](https://support.conserv.io/knowledge/introduction?hsLang=en)
- [Technical Details and Specifications](https://support.conserv.io/knowledge/technical-details-and-specifications?hsLang=en#main-content)

    - [Sensor Specifications](https://support.conserv.io/knowledge/technical-details-and-specifications?hsLang=en#sensor-specifications)
    - [Other Sensor Information](https://support.conserv.io/knowledge/technical-details-and-specifications?hsLang=en#other-sensor-information)
    - [Gateway Specifications](https://support.conserv.io/knowledge/technical-details-and-specifications?hsLang=en#gateway-specifications)
    - [Conserv Cloud Specifications](https://support.conserv.io/knowledge/technical-details-and-specifications?hsLang=en#conserv-cloud-specifications)
- [Installation and Setup](https://support.conserv.io/knowledge/installation-and-setup?hsLang=en#main-content)

    - [Initial Setup](https://support.conserv.io/knowledge/installation-and-setup?hsLang=en#initial-setup)
    - [Add, Move, Swap and Merge Sensors](https://support.conserv.io/knowledge/installation-and-setup?hsLang=en#add-move-swap-and-merge-sensors)
- [Configure Conserv Cloud](https://support.conserv.io/knowledge/configure-conserv-cloud?hsLang=en#main-content)

    - [Organize and Manage Locations and Spaces](https://support.conserv.io/knowledge/configure-conserv-cloud?hsLang=en#organize-and-manage-locations-and-spaces)
    - [Import Data](https://support.conserv.io/knowledge/configure-conserv-cloud?hsLang=en#import-data)
    - [Configure Levels](https://support.conserv.io/knowledge/configure-conserv-cloud?hsLang=en#configure-levels)
    - [Configure Events and Alerts](https://support.conserv.io/knowledge/configure-conserv-cloud?hsLang=en#configure-events-and-alerts)
- [Profile and Account Management](https://support.conserv.io/knowledge/profile-and-account-management?hsLang=en)
- [Manage Sensors](https://support.conserv.io/knowledge/manage-sensors?hsLang=en)
- [Integrated Pest Management](https://support.conserv.io/knowledge/integrated-pest-management?hsLang=en)
- [Analytics and Reports](https://support.conserv.io/knowledge/analytics-and-reports?hsLang=en#main-content)

    - [Manage Analytics Data](https://support.conserv.io/knowledge/analytics-and-reports?hsLang=en#manage-analytics-data)
    - [Preservation Metrics](https://support.conserv.io/knowledge/analytics-and-reports?hsLang=en#preservation-metrics)
    - [Reports](https://support.conserv.io/knowledge/analytics-and-reports?hsLang=en#reports)
- [Mobile app](https://support.conserv.io/knowledge/mobile-app?hsLang=en)
- [Troubleshooting](https://support.conserv.io/knowledge/troubleshooting?hsLang=en#main-content)

    - [Troubleshoot Conserv Cloud Issues](https://support.conserv.io/knowledge/troubleshooting?hsLang=en#troubleshoot-conserv-cloud-issues)
    - [Troubleshoot Sensor Issues](https://support.conserv.io/knowledge/troubleshooting?hsLang=en#troubleshoot-sensor-issues)
    - [Troubleshoot Gateway Issues](https://support.conserv.io/knowledge/troubleshooting?hsLang=en#troubleshoot-gateway-issues)
    - [Troubleshoot Conserv Cloud Mobile App Issues](https://support.conserv.io/knowledge/troubleshooting?hsLang=en#troubleshoot-conserv-cloud-mobile-app-issues)
- [Community, Support, and Updates](https://support.conserv.io/knowledge/community-support-and-updates?hsLang=en)

- [Support](https://support.conserv.io/knowledge)
- [Blog](https://support.conserv.io/blog)

[![Chill listening crop-3](https://support.conserv.io/hs-fs/hubfs/Cnsrv_wmM_mix_rgb-1.png?width=108&height=24&name=Cnsrv_wmM_mix_rgb-1.png "Chill listening crop-3")](https://conserv.io)

<https://www.linkedin.com/company/teamconserv/>

Copyright © 2026, Conserv Solutions Inc.