Salesforce doesn't learn anything new. It just gets what it was missing.
fieldbrain writes Opportunities the way your team configured them, not the way a generic template expects.
The technical precision
Before fieldbrain writes a stage, it reads your actual, currently active StageName picklist from Salesforce itself, once per sync. Only a value confirmed to exist in your exact configuration ever gets written. If no confident match exists, the stage stays unchanged, instead of a wrong or rejected write.
What actually syncs
What stays unchanged: fieldbrain only ever writes the fields from the table above. Other objects, your own automations, layouts, or reports in your CRM stay untouched. Nothing gets deleted, renamed, or restructured, only added to.
A day with Salesforce
A field rep leaves a meeting and speaks three sentences into their phone: what was discussed, who decided, what happens next. fieldbrain turns that into an Opportunity and writes the stage from your real Salesforce configuration. Sales leadership sees the updated pipeline the same day, without anyone catching up on a form that evening.
Does our team need to adjust our sales stages for fieldbrain?
No. fieldbrain reads your current StageName configuration itself before every write and only ever writes values that genuinely exist in it.
What happens if Salesforce hits a rate limit?
fieldbrain automatically retries the write with increasing wait time and respects any Retry-After Salesforce sends. A brief limit doesn't cost you a sync attempt.
Security & Permissions
Your connection belongs exclusively to your account. No other user, not even on the same team, can access it.
Sync is part of the Professional plan and above. Without an active plan it stays inactive, nothing runs in the background.
Disconnect it and sync stops immediately. Data already transferred stays where it is, nothing is retroactively deleted.