Decide which app may win when two business records disagree

Separate authority from transport direction

HubSpot’s data-sync documentation, checked 7 November 2026, treats sync direction and the default conflict-resolving app as separate settings. The conflict choice does not override direction, and an empty value in that default app does not overwrite the other app’s value. Confirm the actual connector’s capabilities rather than assuming every integration follows this behavior.

List the business fields that both systems can edit, using synthetic values only. For each, name the owner of the fact and the permitted destination of changes. A team may maintain a service region in one system and a support classification in another. Calling one app the source of truth for everything can hide those different responsibilities and invite inappropriate overwrites.

Write a field-authority matrix

Create columns for field meaning, authorized editor, permitted direction, conflict decision and unresolved-state handling. Separate the authority rule from timestamps. The newest value is not automatically the most accurate if it was copied from an old import, calculated under a different definition or entered by a team that does not own the fact.

Use concrete opposing values to expose disagreements. If one app says a fictional account is served by the north team and the other says the central team, specify who resolves that contradiction and what should remain unchanged while it is unresolved. Do not use consent, suppression or access-control fields as convenient test data. Their valid user choices and security boundaries cannot be weakened by a generic conflict winner.

Test opposing edits and missing values

Prepare a sequence with an agreed starting state, an allowed edit from each side, a simultaneous disagreement and a missing source value. Write the expected state of both systems after each step. Keep an explicit no-change outcome where the contract does not permit a write; an unchanged destination can be correct rather than evidence that synchronization failed.

Ask the technical owner to show the actual mapping and configured direction for the fixture. Compare the observed state with the matrix, including any connector-specific exclusions. A successful transfer of one field does not prove that another field has the same authority rule. If the available configuration is coarser than the business contract, record the mismatch and consider a narrower authorized integration rather than silently accepting broad overwrite power.

Make unresolved conflicts visible

The final record should distinguish an expected winning value, a prohibited write, an unsupported configuration and a genuine unresolved discrepancy. Route each category to its appropriate owner. Do not repeatedly reverse the two values by hand while leaving the conflicting synchronization logic running; that can conceal the cause and produce a cycle of unexplained changes.

Retain the synthetic sequence as an acceptance test for connector revisions and changes in field ownership. Note the account context and documentation date without promising universal last-write behavior. The exercise ends with a reviewable authority matrix and observed exceptions. It does not connect apps, grant ongoing access, change live mappings or authorize replacement of customer-controlled information.

Make the reasoning concrete.

A fictional subscription business stores its commercial account segment in a sales app and its service handling class in a support app. A proposed two-way connection maps both into one field and selects the sales app as the global winner.

The team rejects the ambiguous shared field and records separate ownership rules before implementation. It treats the connector’s configuration limit as a design constraint, not permission to overwrite the support team’s meaning.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Meaning

   What exact business fact does this field represent?

2. Authority

   Which owner may establish or correct that fact?

3. Direction

   Which writes are permitted between the two systems?

4. Conflict

   What happens to opposing or missing values?

5. Exception

   Which unsupported or unresolved cases must remain visible?

Watch for the wrong conclusion.

• Equating the most recently copied value with the authoritative fact.
• Assuming the conflict winner can override a one-way connection.
• Using sync rules to restore a more permissive customer preference.

Sources & scope

Workflows, fixtures, worksheets and examples are original editorial analysis. Sources support the narrow attributed statements, not measured business results. Platform guidance is scoped to the documented implementation and date checked. Synthetic acceptance only; no external changes, messages or permissions are performed.

• Connect and use HubSpot data sync →Primary platform documentation · Supports: Supports the documented separation of sync direction, conflict priority and missing-value behavior. The field-authority contract and test sequence are original.