FAQs

Customer experience (CX) covers the customer's overall relationship with a business, including physical, human, and digital interactions. Digital customer experience focuses specifically on interactions that happen through digital channels. DCX is therefore a part of the broader CX, not a replacement for it.

Key elements include an easy-to-navigate digital experience, consistent interactions across channels, relevant personalization, accessible content, fast and reliable performance, and connected customer support. The goal is to make the journey feel coherent rather than like a series of disconnected interactions.

Digital touchpoints are often where customers first interact with a business and where much of the customer journey takes place. A slow website, confusing checkout, or disconnected support experience can affect the overall perception of a brand, even when the underlying product or service is good.

Digital customer experience (DCX) is the experience customers have when interacting with a business through digital touchpoints such as websites, mobile apps, chat, email, social media, and self-service portals. It covers the full digital journey, from discovering a brand to making a purchase, getting support, and staying engaged.

Create a URL mapping before migration, preserve existing URLs where practical or use 301 redirects for changed URLs, and validate internal links, canonical URLs, metadata, indexability, and XML sitemaps after launch. Also check migrated images and content for references to the old WordPress domain. A migration can cause temporary ranking fluctuations, so monitor search performance after the site goes live.

You have two main options: recreate the original WordPress URL structure as Drupal aliases or create new Drupal aliases and use 301 redirects from the old URLs to their new equivalents. Pathauto can generate new aliases based on defined patterns, while Redirect can manage permanent redirects. Plan your URL mapping before the migration rather than trying to fix broken URLs afterward.

For a standard WordPress site, the simplest approach is WXR export + WordPress Migrate. Export all content from WordPress, install WordPress Migrate and its supporting modules in Drupal, configure the mappings through the migration wizard, and execute the migrations. More complex sites may benefit from the SQL-based WordPress Migrate SQL approach.

First, create the required Drupal content types, fields, and taxonomy vocabularies. Then use the WordPress Migrate wizard to map WordPress posts, pages, categories, tags, and featured images to their corresponding Drupal structures. For custom or unsupported fields, you may need custom Migrate process plugins or migration configuration.

A standard WXR migration can bring over posts, pages, comments, attachments, categories, tags, and other exported content such as custom fields. However, highly customized WordPress data, including some custom post types, plugin-specific fields, and Gutenberg structures, may require additional migration logic.

Yes. The WordPress Migrate module can automatically import WordPress posts, pages, comments, attachments, categories, and tags from a WXR export. You can configure the migration through Drupal's UI or run it with Drush using drush migrate:import --all.