Answers.Body: <p>Regarding the &quot;update&quot; section: perhaps you want to stick to a specific version of CiviCRM package:  using Composer it should be like this (just drop the tilde):</p>
  <pre><code> &quot;require&quot;: {
      &quot;civicrm/civicrm-core&quot;: &quot;5.55&quot;,
      &quot;civicrm/civicrm-drupal-8&quot;: &quot;5.55&quot;,
      &quot;civicrm/civicrm-packages&quot;: &quot;5.55&quot;,
  </code></pre>
  <p>Check for instance <a href="https://stackoverflow.com/questions/40914114/how-to-install-a-specific-version-of-package-using-composer">this</a> for tech details.</p>
  <p>On the separate note: despite of D7 hard EOL announced, I'd stick with it for a bit longer its &quot;expiration date&quot;, maybe a few years more. Per my experience, the current state of D8/9/10 and its CiviCRM counterpart doesn't quite worth an upgrade rush, to put it politely.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-10-20T09:49:48.210Z
Answers.LastActivityDate: 2023-10-20T09:49:48.210Z
Answers.UserDisplayName: yurg
Body: <p>I've been using CiviCRM on Drupal 7 for many years, and it's time to upgrade my Drupal.</p>
  <ul>
  <li>Drupal 8 went EOL November 2, 2021.</li>
  <li>Drupal 9 goes EOL November 1, 2023, which is in 12 days.</li>
  </ul>
  <p>So it looks like Drupal 10 should be the way to go.</p>
  <p>I'm starting with a fresh Drupal installation (I have a very minimal website outside of CiviCRM), I don't really need to port any Drupal-level stuff over to the new site.</p>
  <p>I went to the relevant installation page <a href="https://docs.civicrm.org/installation/en/latest/drupal/" rel="nofollow noreferrer">https://docs.civicrm.org/installation/en/latest/drupal/</a> , but the instructions there don't seem to support D10 yet (they ask for pull requests to write such instructions - wish I could help!).</p>
  <p>I'm guessing I need to do something like:</p>
  <pre><code>cd /opt/my-dir
  composer remove drush/drush  # Is this still necessary?
  composer config extra.enable-patching true
  composer config minimum-stability dev
  composer require civicrm/civicrm-{core,packages,drupal-8}:'~5.55'  # Should this be drupal-10 now?
  composer require 'drush/drush:12.*'
  </code></pre>
  <p>Does that all seem correct?  CiviCRM 5.55 is my current version.</p>
  <p>Once I've done this, what's the best procedure for importing all my data from my current installation?  I see <a href="https://docs.civicrm.org/sysadmin/en/latest/misc/switch-servers/" rel="nofollow noreferrer">https://docs.civicrm.org/sysadmin/en/latest/misc/switch-servers/</a> but that also looks quite old, I'm not sure what's best practice.</p>
  <p><strong>UPDATE:</strong> I tried out this technique and I seem to have ended up with CiviCRM 5.66 installed, despite seeing the following in my <code>composer.json</code> file:</p>
  <pre><code>    &quot;require&quot;: {
          &quot;civicrm/civicrm-core&quot;: &quot;~5.55&quot;,
          &quot;civicrm/civicrm-drupal-8&quot;: &quot;~5.55&quot;,
          &quot;civicrm/civicrm-packages&quot;: &quot;~5.55&quot;,
  </code></pre>
  <p>How can I keep version parity with the site I'm coming from?</p>
  
Tags: <drupal><installation><migration>
Title: Unclear on install instructions - D10?
ThreadText: # Unclear on install instructions - D10?
  
  (Asked by: username_0 on 2023-10-20)
  
  I've been using CiviCRM on Drupal 7 for many years, and it's time to upgrade my Drupal.
  
  Drupal 8 went EOL November 2, 2021.
  Drupal 9 goes EOL November 1, 2023, which is in 12 days.
  
  So it looks like Drupal 10 should be the way to go.
  I'm starting with a fresh Drupal installation (I have a very minimal website outside of CiviCRM), I don't really need to port any Drupal-level stuff over to the new site.
  I went to the relevant installation page https://docs.civicrm.org/installation/en/latest/drupal/ , but the instructions there don't seem to support D10 yet (they ask for pull requests to write such instructions - wish I could help!).
  I'm guessing I need to do something like:
  cd /opt/my-dir
  composer remove drush/drush  # Is this still necessary?
  composer config extra.enable-patching true
  composer config minimum-stability dev
  composer require civicrm/civicrm-{core,packages,drupal-8}:'~5.55'  # Should this be drupal-10 now?
  composer require 'drush/drush:12.*'
  
  Does that all seem correct?  CiviCRM 5.55 is my current version.
  Once I've done this, what's the best procedure for importing all my data from my current installation?  I see https://docs.civicrm.org/sysadmin/en/latest/misc/switch-servers/ but that also looks quite old, I'm not sure what's best practice.
  UPDATE: I tried out this technique and I seem to have ended up with CiviCRM 5.66 installed, despite seeing the following in my composer.json file:
      "require": {
          "civicrm/civicrm-core": "~5.55",
          "civicrm/civicrm-drupal-8": "~5.55",
          "civicrm/civicrm-packages": "~5.55",
  
  How can I keep version parity with the site I'm coming from?
  
  **Tags:** drupal, installation, migration
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2023-10-20. Score: 1 | Accepted answer
  
  Regarding the "update" section: perhaps you want to stick to a specific version of CiviCRM package:  using Composer it should be like this (just drop the tilde):
   "require": {
      "civicrm/civicrm-core": "5.55",
      "civicrm/civicrm-drupal-8": "5.55",
      "civicrm/civicrm-packages": "5.55",
  
  Check for instance this for tech details.
  On the separate note: despite of D7 hard EOL announced, I'd stick with it for a bit longer its "expiration date", maybe a few years more. Per my experience, the current state of D8/9/10 and its CiviCRM counterpart doesn't quite worth an upgrade rush, to put it politely.
  
  
  ---
  
  