An opportunity’s pipeline, stage and status represent distinct choices. Avoid matching stages only by display name.
Before you beginConfirm the authorized account, required operations, scopes and records used for a controlled test.
Step by step
- Inventory the source states and the destination pipeline and stage identifiers.
- Define what each mapped state means, including unmapped and closed outcomes.
- Read the current opportunity create, update, status and upsert contracts; choose the narrowest appropriate operation.
- Verify the contact and opportunity identity before changing state. Consider workflows triggered by those changes.
- Test the intended transition and a non-matching case with controlled records.
- Re-read the result and record safe IDs. Reconcile uncertain writes before attempting another transition.
Expected result
The destination opportunity has the intended identity, pipeline, stage and status.
Troubleshooting
- A renamed stage should not silently change an established identifier mapping.
- Do not mark a deal won merely because a source record was created.
- Review downstream workflow effects before a bulk synchronization.
Supporting documentation
These links open the provider’s documentation. Availability and permissions depend on your account.
More guides
Start a scoped CentriCRM integrationSelect authentication, verify account context and scopes, and plan webhook handling before enabling writes.
Synchronize contacts without replacing unrelated dataUse account identity, duplicate policy and narrow updates deliberately.
Read calendar availability safelyKeep calendar identity, range and timezone explicit.
Separate message history from outbound sendingVerify the operation’s effect before using conversation APIs.