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.

If you are weighing whether to upgrade to Drupal 8 but aren’t sure what kind of budget to expect, we’re going to breakdown the upgrade (migration) process. Along the way, we'll highlight the factors that will add hours to your project.

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...

The Migrate API is almost stable and the majority of its basic functions and ways that folks interface with it are are to see the state of a migration, execute (import) a migration, or revert (rollback) a migration.

If you need to migrate field collections from Drupal 7 into Drupal 8, here's a walk through of how to do it. But before you start reading, I'd like you to stop and see how you can make this process better.

MTech specializes in Drupal migrations and upgrades.

As you might know, the Datetime Range module is currently an experimental module within Drupal 8 core.

Thanks to the drupaleros community, Drupal 8 has two new plugins added in the migrate plus module: entity_lookup and entity_generate. These can be used to lookup and create an entity if it does not exist.