<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>migrating content</title><description/><link>https://kevinquillen.com</link><language>en</language><item><title>Migrating Field Groups from Features in Drupal 7 to Drupal 9</title><link>https://kevinquillen.com/migrating-field-groups-features-drupal-7-drupal-9</link><guid isPermaLink="false">347 at https://kevinquillen.com</guid><description>
&lt;span property=&quot;schema:name&quot;&gt;Migrating Field Groups from Features in Drupal 7 to Drupal 9&lt;/span&gt;

            &lt;div property=&quot;schema:text&quot; class=&quot;text-content clearfix field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;I am in the midst of a Drupal 7 to Drupal 9 upgrade for a client. This is the first time I am using the Migrate Drupal and Migrate Drupal UI core modules to do an inline upgrade. So far everything has been great. I just need to drop in a data migration path for some Paragraphs and recreate a couple Views and we should be good.&lt;/p&gt;

&lt;p&gt;However, when I was checking around on some content, I noticed I had no field groups in the new site. Why? Field Groups comes with a Field Groups Migrate submodule, which will pick up and migrate any field groups in a Drupal 7 site to Drupal 8 or 9.&lt;/p&gt;&lt;/div&gt;
      
&lt;span rel=&quot;schema:author&quot;&gt;&lt;span lang about=&quot;https://kevinquillen.com/user/1&quot; typeof=&quot;schema:Person&quot; property=&quot;schema:name&quot; datatype&gt;Kevin&lt;/span&gt;&lt;/span&gt;

&lt;span property=&quot;schema:dateCreated&quot; content=&quot;2021-03-12T12:12:03+00:00&quot;&gt;&lt;time datetime=&quot;2021-03-12T07:12:03-05:00&quot; title=&quot;Friday, March 12, 2021 - 07:12&quot;&gt;March 12th, 2021&lt;/time&gt;
&lt;/span&gt;
</description><pubDate>Fri, 12 Mar 2021 12:12:03 GMT</pubDate><dc:creator>Kevin</dc:creator></item><item><title>Add 301 Redirects to a Drupal Migration</title><link>https://kevinquillen.com/add-301-redirects-drupal-migration</link><guid isPermaLink="false">305 at https://kevinquillen.com</guid><description>
&lt;span property=&quot;schema:name&quot;&gt;Add 301 Redirects to a Drupal Migration&lt;/span&gt;

            &lt;div property=&quot;schema:text&quot; class=&quot;text-content clearfix field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;Migrating content from one platform to another saves lots of time from doing grunt work and gets data moved fast. However, simply moving the content doesn’t mean the job is done. There are other considerations too, such as 301
redirects for example. Since we are moving content, our aliases are likely changing too. We can create 301s while migrating content in all at once.&lt;/p&gt;

&lt;p&gt;The way I like to do it is to place the following in my Migration class &lt;code&gt;complete()&lt;/code&gt; method:&lt;/p&gt;&lt;/div&gt;
      
&lt;span rel=&quot;schema:author&quot;&gt;&lt;span lang about=&quot;https://kevinquillen.com/user/1&quot; typeof=&quot;schema:Person&quot; property=&quot;schema:name&quot; datatype&gt;Kevin&lt;/span&gt;&lt;/span&gt;

&lt;span property=&quot;schema:dateCreated&quot; content=&quot;2014-07-02T08:02:00+00:00&quot;&gt;&lt;time datetime=&quot;2014-07-02T04:02:00-04:00&quot; title=&quot;Wednesday, July 2, 2014 - 04:02&quot;&gt;July 2nd, 2014&lt;/time&gt;
&lt;/span&gt;
</description><pubDate>Wed, 02 Jul 2014 08:02:00 GMT</pubDate><dc:creator>Kevin</dc:creator></item></channel></rss>