PCO Sync V2

PCO Sync V2 keeps Rock and Planning Center Online in sync—automatically. Updates in one system show up in the other, so your team data stays accurate and consistent across both.

*Note: Only Actively serving people in Planning Center Services are synced.

First things first:

Here's what you'll need to prep for PCO Sync v2:

  • Make sure you're running Rock RMS v14.0 or higher.
  • You’ll need a 9 Embers PCO Sync V2 subscription ($300/year).
  • You'll need admin rights in PCO.

If you do not have a PCO Sync V2 account, follow this link to the PCO Sync V2 Subscription Request. It’s just a quick form, and you’ll get setup instructions faster than you can say workflow.

Choose Applicable Installation Instructions:

I’m already using the original PCO Sync (v1)

Instructions to Install V2 with V1 Installed

I’m not using any PCO sync (yet!)

Instructions for Fresh Install PCO Sync 2

Prefer video instructions instead? You're in luck! Click the appropriate link below for step-by-step video guides.

Installing PCO Sync V2 with V1 already installed

Installing PCO Sync V2 (fresh Install)

FAQ

Q: I used the Folder Import and now I have a TON of groups I don’t need. Can I bulk delete them?

A: Yep! Just fill our Plugin support form here—we have a SQL script that can remove the whole folder hierarchy in one swoop.

Q: Do I need access to PCO?

A: Yes. You need admin-level access to generate tokens and manage integrations.

Q: Is Rock or PCO the primary source of information?

A: Neither. This is a true 2-way sync. The most recently updated record—whether in Rock or PCO—will be used to sync data.

Q. The Sync failed because of a Fatal Request Error. How do I fix this? 

A: This is likely due to a group in Rock still linked to a team/position in PCO that was deleted. PCO doesn't delete a team from their database until 30 days after someone deletes it in the UI. Our update to PCO Sync V2 1.8 (available soon) is made to handle these situations. Updating the plugin should resolve this issue.

Q. I received an error that "Person could not be added. Matched person is already being synced." What does this mean?

A: This error usually indicates duplicate records in Planning Center. The sync finds a profile in Planning Center that isn’t yet linked to a profile in Rock, but it also finds a matching person in Rock who is already linked to a different Planning Center profile.

To fix this:

  • Check for and merge any duplicates in Planning Center.
  • After merging, review the sync’s person mapping to confirm that the correct Planning Center ID is linked to the correct person in Rock for those records.

Support

If you need assistance, please fill out our Plugin Support Form and select the type of support you need:

  • I need help setting up my PCO Sync V2 subscription.
  • I'm already using the PCO plug-in and I'm having issues.
  • I'm using a different plug-in and I'm having issues.

Before submitting a new issue, we recommend reviewing our 9 Embers Plug-in Issues List on GitHub to see if your concern has already been documented. If your issue isn’t listed, please provide as much detail as possible in the form to help us assist you efficiently.

Additional Support for PCO V2 Users

If you're using the PCO Sync V2 plug-in and need more in-depth assistance, we offer an optional 30-minute Zoom support call for a one-time fee of $100. Ongoing or additional support may be available upon request at a rate of $175 per hour. To request this support, please select the “I’m already using the PCO plug-in and I’m having issues” option on the Plug-in Support Form.

Top