A day doesn't go by that someone isn't asking a question in Slack #migration about how to troubleshoot a specific problem with a tricky migration.

One of the things I constantly get asked about in the Drupal 8 migrate space is when will migrate be ready for use. With the API being marked stable in 8.5.0, now is a good time to consider upgrading. Upgrading a D6 or D7 site should be ready, especially if you have mainly core modules in use.

Today, the final blocker for Migrate Drupal UI was committed. That leaves only a series of complicated internationalization (i18n) issues to get resolved for Migrate Drupal before all of migrate in all of Drupal core can be considered stable.

For those following along from the sidelines, Drupal 8 core has 3 modules that make up the migrate sub-system. For the past few years, the community has been working very hard to get these to a stable state an out of their "experimental" designation. Drum role please...

As the maintainer of the popular D8 Migrate Source CSV contrib module, it is about time I wrote how to use the thing. It is similar to a core migration, except you have to already create the destination node, taxonomies, etc.

There's been a series of questions pop up in #drupal-migrate in IRC over the past few days and weeks about how to handle configuration management for migrations. There's several options available, I’d like to suggest one that seems to work really well for us (and maybe you as well).

In a recent client project (most of my good ideas come from solving client problems), I had the dilemma of exposing an entity reference with-in a standard Drupal FAPI form. It needed to have auto complete functionality to search for a Commerce Product by SKU.

 like Git way better than all the alternatives. I learn more things about it all the time. Even today, I wondered if there was an easier way to create nicely named patches automatically; and there is. Here's a run down of the more common tips and tricks I've learned.

I had a wonderful chance to partake in an impromptu code sprint at DrupalCon Portland to help with the recovery of Moore, OK. I learned a lot; but more importantly I got to help with something that will have lasting impact on people recovering from the devestation of the recent tornado.

Here's the requirements. You have a parent-child relationship (one-to-many) between two content types. There are three media related fields on these content types. Your assignment is to display the first populated field in a block for a panels managed page.