Been there with different integration setups. The plugins don’t clash directly since they work independently, but you’ll get duplicate entries if both are active on the same forms.
I hit this exact issue last year with a client. Had their custom Salesforce integration running smooth for months, then they wanted to test the official extension. Big mistake leaving both enabled during testing.
What worked: I mapped out which forms used the old integration first. Then disabled the third-party plugin completely before setting up the official one. No conflicts, just had to reconfigure the field mappings.
The official extension is solid now - handles custom fields better than most third-party options I’ve used. Migration was straightforward once I stopped trying to run both at once.
This walkthrough covers the setup process if you decide to switch:
Just document your current field mappings before switching. Makes the transition way smoother.