System of recordThe system allowed to be right about a fact. The CRM is rarely the system of record for an invoice or a stock count.

DirectionWhich system is allowed to write a field. One-way means only one side may change it. Two-way means both may, and you need a winner.

Match keyThe value that says two records are the same person, company, or order. Email, account number, and order id are common keys. A display name is not.

DedupeThe rule that stops a second contact or company when the key already exists. Run it before the first full sync, not after the duplicates are in both systems.

ConflictBoth sides changed the same field since the last sync. Someone has to win, and the loser should be logged.

Field mapThe list of which source field lands in which target field, including the fields you refuse to sync.

ObjectThe kind of record: contact, company, deal, order, invoice, product. A connector that only moves contacts will not move the order.

Native connectorThe app the vendor ships. It maps what they chose to map, on their schedule.

iPaaSA tool such as Zapier, Make, or Workato that runs the steps between systems. A person still owns the scenario.

Custom APICode your team maintains. Use it when the map itself is the product, and budget for the rate limit.

WebhookA push when a record changes. It is faster than a nightly pull, and it fails quietly if nobody watches the retries.

PollingA scheduled read of what changed. Simpler than a webhook, and late by however long the schedule is.

Rate limitHow many calls a system will accept in a window. A retry storm is what happens when a failure keeps asking.

WritebackA change sent from HubSpot into the source system. It needs an owner. A dashboard should not write back on a timer.

IdempotentRunning the same sync twice does not create a second record. If it does, the key is wrong.

SandboxA copy of the system used to test the map. A successful sandbox run is not proof the production keys match.