Answers.Body: <p>I would always recommend to have CiviCRM on a separate server from the public facing website (privacy, security and updates) even thought it is more cumbersome and more expensive.</p>
  
  <p>So I assume you will have 3 WP websites, and one central CiviCRM (in a dummy Drupal or WP). I would use CiviProxy to ensure only whitelisted API calls are accepted (check <a href="https://github.com/systopia/CiviProxy" rel="nofollow noreferrer">https://github.com/systopia/CiviProxy</a> for a little more info) and then there are a few options I think:</p>
  
  <ol>
  <li>Ensure your WP sites can process the data and prepare an API call to CiviCRM using the core API's</li>
  <li>Use the work done on Gravity Forms with CiviCRM although I am not sure that will work with REST</li>
  <li>Just throw all the data on a Wordpress form to CiviCRM and create a customized extension that provides specific API calls to process the data. We have done this with the CiviCRM Contact Form 7 plugin and specific API's.</li>
  </ol>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-04-20T12:57:47.723Z
Answers.LastActivityDate: 2017-04-20T12:57:47.723Z
Answers.UserDisplayName: ErikH - CiviCooP
Body: <p>Which approach would you recommend for integrating CiviCRM into an existing ecosystem of 3 Wordpress installations, each residing on its own server with its own domain, where at the moment users, event-registrations and newsletters are being managed separately?</p>
  
  <p>Ideally changes in one of the clients would update the central CiviCRM database (via REST et al.) and vice versa.</p>
  
Tags: <wordpress><multisite>
Title: One CiviCRM for multiple sites
ThreadText: # One CiviCRM for multiple sites
  
  (Asked by: username_0 on 2017-04-20)
  
  Which approach would you recommend for integrating CiviCRM into an existing ecosystem of 3 Wordpress installations, each residing on its own server with its own domain, where at the moment users, event-registrations and newsletters are being managed separately?
  
  Ideally changes in one of the clients would update the central CiviCRM database (via REST et al.) and vice versa.
  
  **Tags:** wordpress, multisite
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-04-20. Score: 1
  
  I would always recommend to have CiviCRM on a separate server from the public facing website (privacy, security and updates) even thought it is more cumbersome and more expensive.
  
  So I assume you will have 3 WP websites, and one central CiviCRM (in a dummy Drupal or WP). I would use CiviProxy to ensure only whitelisted API calls are accepted (check <https://github.com/systopia/CiviProxy> for a little more info) and then there are a few options I think:
  
  1. Ensure your WP sites can process the data and prepare an API call to CiviCRM using the core API's
  2. Use the work done on Gravity Forms with CiviCRM although I am not sure that will work with REST
  3. Just throw all the data on a Wordpress form to CiviCRM and create a customized extension that provides specific API calls to process the data. We have done this with the CiviCRM Contact Form 7 plugin and specific API's.
  
  
  ---
  
  