---
title: "Hudu Integration: Customer Sync"
url: "https://help.psarev.io/en/article/hudu-integration-customer-sync"
language: "en"
last_updated: "2026-11-18T16:35:18.111Z"
---

# Hudu Integration: Customer Sync

The link between a Hudu company and a Rev.io customer is the foundation of the Hudu integration. Devices and passwords always belong to a linked customer, and nothing syncs for a customer until its company link is accepted.

For each Hudu company that isn't linked yet, the integration looks for the matching Rev.io customer in the following order. Only customers that aren't linked yet are considered.

1.  **Website match.** The company's website in Hudu matches a customer's website in Rev.io.
2.  **Company name match.** The names are a close match, such as Acme Corporation and Acme Corp.

A match is always a suggestion and is never linked automatically. Every match waits on the **Data Sync & Mapping** page for you to confirm. If a company name closely matches more than one customer, such as Acme - Dallas and Acme - Austin, the integration doesn't guess and queues the company for you to choose. A customer that is already linked, or already suggested for another company, isn't offered again.

What happens when no customer matches depends on the **Auto-Create Rev.io Customers** setting.

| **Option** | **Definition** |
| --- | --- |
| **On** | *Creates a new customer in Rev.io and links it automatically.* |
| **Off** | *Queues the company on the **Data Sync & Mapping** page, where you can link it to an existing customer or create a new one. Nothing is created.* |

When the integration creates a customer, it does the following.

-   Uses the Hudu company's name, website, and address.
-   Fills any missing address fields from the **Default Customer Address** settings, because Rev.io needs an address to create a customer.
-   Creates the customer as a **Business** customer with an **Open** status.
-   Places the customer under its parent customer, if the company's parent in Hudu is already linked.
-   Writes the new Rev.io customer number into the Hudu company's **Id in Integration** field, so you can see the link from Hudu.

If creating a customer fails, for example because Rev.io was briefly unavailable, the company stays on the **Data Sync & Mapping** page and the integration tries again on a later run. It checks first whether the earlier attempt went through, so a retry doesn't create a duplicate customer.

The following actions are available for each company on the **Data Sync & Mapping** page. Each row shows the company's details from Hudu, including its address.

-   Accept the suggested customer to confirm the link and start syncing.
-   Choose a different customer if the suggestion is wrong, and then accept it.
-   Create a new customer for a company that has no match.
-   Reject a suggestion that isn't right.
-   Click **Confirm All & Finalize** when you finish the list, so the asset sync starts right away for the customers you confirmed. Links accepted one at a time are picked up on the next scheduled run.

See the [Integrations Library: Data Sync & Mapping](https://help.psarev.io/en/article/integrations-library-data-sync-mapping) article for more information.

Once a company is linked, the integration keeps it current in both directions on each run. Which system wins for the company name and address depends on the **Account Info Conflict Policy** setting.

| **Option** | **Definition** |
| --- | --- |
| **Don't overwrite** | *Neither system changes the other. Once a company is linked, its name and address are maintained separately in each system.* |
| **Rev.io is the source of truth** | *Rev.io values are written to Hudu. Hudu values never overwrite Rev.io.* |
| **Hudu is the source of truth** | *Hudu values are written to Rev.io. Rev.io values never overwrite Hudu.* |
| **Most recent change wins** | *The system that was edited since the last sync updates the other. If both were edited, the later edit wins.* |

Some fields follow the same rules under every policy, as described below.

| **Field** | **Definition** |
| --- | --- |
| **Company name** | *Follows the policy in both directions.* |
| **Address** | *Street, line 2, city, state, and ZIP follow the policy in both directions.* |
| **Country** | *Follows the policy from Hudu to Rev.io. Country is not sent to Hudu.* |
| **Website** | *Always syncs in both directions.* |
| **Parent company** | *Always syncs in both directions once the parent is linked. Parents are handled first so the hierarchy carries over.* |
| **Phone** | *Not synced, because Rev.io customers don't have a phone field.* |

The policy only applies to customers that are already linked. A blank value on one side never erases a real value on the other, and records are only updated when something changed.

When a customer is created from a Hudu company with no address, the address comes from the **Default Customer Address** settings. With the shipped values, address line 1 is **TBD**. A TBD address is replaced automatically, on both the service and billing address, once the Hudu company has a full address with street, city, state, and ZIP. This happens under every conflict policy. If you change address line 1 to something other than TBD, such as your office address, customers created with it keep that address unless the conflict policy lets Hudu overwrite it. A real Rev.io address is never replaced by this rule.

To limit which customers sync, enter a tag in the **Sync Tag** setting. Only Rev.io customers with that tag stay in sync in both directions, along with their assets and passwords. The following rules apply.

-   Customers without the tag are paused, not unlinked. Nothing is deleted, and they resume as soon as they are tagged.
-   New Hudu companies are still matched or created, because a customer that doesn't exist yet can't have the tag. Add the tag to the new customer in Rev.io to keep it syncing.
-   Leave the setting blank to include all customers.

| **NOTE:** A good way to roll out the integration is to tag two or three customers, enter that tag in the **Sync Tag** setting, and finish setup. Once you're happy with those customers, clear the setting to include everyone. |
| --- |

For more information about the Hudu integration, see the following articles.

[Hudu Integration: Overview](https://help.psarev.io/en/article/hudu-integration-overview)  
[Hudu Integration: Asset Sync](https://help.psarev.io/en/article/hudu-integration-asset-sync)  
[Hudu Integration: Configuration](https://help.psarev.io/en/article/hudu-integration-configuration)
