<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Complex CMS Migration Service - Migrate Content (Posts about planning)</title><link>https://migratecontent.com/</link><description></description><atom:link href="https://migratecontent.com/categories/planning.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Sun, 22 Mar 2026 16:22:30 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>How to Prepare for Your Drupal to WordPress Migration</title><link>https://migratecontent.com/how-to-prepare-drupal-wordpress-migration/</link><dc:creator>Aiden</dc:creator><description>&lt;p class="intro"&gt;The most successful migrations I've worked on share one thing in common: the site owner did their preparation before the project started. A few hours of groundwork on your side (auditing your content, gathering credentials, and clarifying your goals) saves significant time and budget during the migration itself. Here's what to have ready.&lt;/p&gt;

&lt;h2&gt;Clarify Your Migration Goals&lt;/h2&gt;

&lt;p&gt;Before discussing timelines or costs, the first question to answer is: what do you actually need from this migration?&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;What must come across?&lt;/strong&gt; All content, or a curated subset? Do you need full order history, or just active products? Complete user accounts, or just administrators?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;What can be left behind?&lt;/strong&gt; Old drafts, test content, unused content types, and deprecated modules don't need to migrate. Stripping these out reduces complexity and cost.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Are you redesigning?&lt;/strong&gt; If you're planning a visual redesign alongside the migration, the WordPress theme work can run in parallel with data migration. If you want to replicate the existing design, that's a different brief.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;What's your timeline?&lt;/strong&gt; A hard deadline (end-of-life pressure, hosting contract expiry, compliance audit) affects how the project is phased.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Clear answers to these questions shape the entire project scope. Ambiguity here is the most common cause of budget overruns.&lt;/p&gt;

&lt;h2&gt;Audit Your Drupal Content&lt;/h2&gt;

&lt;p&gt;The content audit is the foundation of the migration plan. I'll conduct a detailed technical audit once the project starts, but having your own understanding of what's on the site accelerates the process considerably.&lt;/p&gt;

&lt;h3&gt;Content Types&lt;/h3&gt;

&lt;p&gt;Log in to your Drupal admin and go to Structure &amp;gt; Content types. List every content type and roughly how many nodes exist for each. Pay particular attention to custom types. These are the ones that require the most migration work.&lt;/p&gt;

&lt;h3&gt;Taxonomy Vocabularies&lt;/h3&gt;

&lt;p&gt;Check Structure &amp;gt; Taxonomy. Note each vocabulary, the number of terms, and whether terms have custom fields or descriptions. Taxonomy structures often need restructuring for WordPress.&lt;/p&gt;

&lt;h3&gt;Media and Files&lt;/h3&gt;

&lt;p&gt;Estimate the volume of uploaded files: images, documents, PDFs, videos. Check whether files are stored in a public or private filesystem. Large media libraries need separate handling during migration.&lt;/p&gt;

&lt;h3&gt;Users and Roles&lt;/h3&gt;

&lt;p&gt;Note how many user accounts exist and which roles are in use. If your site has authenticated user features (member areas, customer accounts, editorial workflows), these need role mapping to WordPress equivalents.&lt;/p&gt;

&lt;h3&gt;Custom Modules and Views&lt;/h3&gt;

&lt;p&gt;List any custom-built modules and key Views configurations. Custom modules may store data in their own database tables, which won't be covered by standard migration scripts. Views-generated pages that drive traffic need equivalent WordPress implementations.&lt;/p&gt;

&lt;h2&gt;Gather Your Credentials&lt;/h2&gt;

&lt;p&gt;Migration requires access to several systems. Having these ready at the start of the project avoids delays:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Database access.&lt;/strong&gt; Credentials for your Drupal database, via cPanel, phpMyAdmin, or direct SSH access. I'll need to export the database for analysis and test migrations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;File system access.&lt;/strong&gt; FTP or SSH credentials to download your &lt;code&gt;sites/default/files&lt;/code&gt; directory. This contains all uploaded media.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Drupal admin login.&lt;/strong&gt; Administrative access to the Drupal backend for reviewing content types, modules, and configuration.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Hosting provider details.&lt;/strong&gt; Your current hosting provider and plan, plus any planned changes. If you're moving hosting alongside the migration, coordination is needed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Domain registrar access.&lt;/strong&gt; For the DNS cutover at launch, you'll need access to update DNS records, or be able to instruct your registrar to do so.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you don't have direct database access, your hosting provider can usually provide it on request. For managed hosting platforms, let me know the provider and I'll advise on the best approach.&lt;/p&gt;

&lt;h2&gt;Plan Your WordPress Architecture&lt;/h2&gt;

&lt;p&gt;These decisions don't need to be finalised before migration starts, but thinking about them early helps:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Theme direction.&lt;/strong&gt; Are you using a custom theme, a pre-built theme, or a theme framework? If you want to replicate your current design, screenshots and a list of key page layouts are helpful.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Essential plugins.&lt;/strong&gt; Identify functionality your Drupal site provides that will need WordPress plugin equivalents: forms, SEO, caching, e-commerce, membership areas.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Hosting environment.&lt;/strong&gt; WordPress hosting requirements differ from Drupal. If you're staying with your current provider, confirm they support WordPress. If moving, hosting selection should happen early in the project.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;SEO Preparation&lt;/h2&gt;

&lt;p&gt;If organic search drives meaningful traffic to your site, SEO preparation should start before the migration project begins.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Export your URL aliases.&lt;/strong&gt; Your Drupal database contains a &lt;code&gt;url_alias&lt;/code&gt; table with every URL path on the site. Export this. It's the starting point for your redirect map.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Export metadata.&lt;/strong&gt; If you're using the Metatag module, export the meta titles and descriptions. These need importing into your WordPress SEO plugin.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Identify high-traffic pages.&lt;/strong&gt; Use Google Analytics or Search Console to identify the pages that drive the most organic traffic. These get priority attention during URL mapping and redirect testing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Document taxonomy pages.&lt;/strong&gt; Check whether any Drupal taxonomy listing pages appear in search results and drive traffic. These need explicit redirect handling.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For a more detailed treatment of SEO during migration, see &lt;a href="https://migratecontent.com/preserving-seo-drupal-wordpress-migration/"&gt;Preserving Your SEO During a Drupal to WordPress Migration&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;What to Expect from the Process&lt;/h2&gt;

&lt;p&gt;A well-run migration isn't a black box. Here's what the process looks like from your side:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Initial audit.&lt;/strong&gt; I analyse your database and content model, then provide a migration plan and quote. No work begins without your sign-off on the scope.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Iterative testing.&lt;/strong&gt; You'll review test migration output at key stages. This is your opportunity to catch issues early: missing fields, incorrect mappings, content that needs restructuring.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Your involvement.&lt;/strong&gt; Plan for a few hours per week during the active migration phase. You'll be reviewing test output, answering questions about content decisions, and signing off on milestones.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Launch coordination.&lt;/strong&gt; The DNS cutover needs to happen during a low-traffic window. For e-commerce sites, I coordinate the final data sync and cutover to minimise disruption.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The total timeline depends on complexity. A straightforward content migration might take 4 to 6 weeks, while a complex site with e-commerce, custom content types, and extensive SEO requirements can run 8 to 12 weeks.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Related reading:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://migratecontent.com/preserving-seo-drupal-wordpress-migration/"&gt;Preserving Your SEO During a Drupal to WordPress Migration&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://migratecontent.com/how-we-migrate-technical-process/"&gt;How We Migrate: The Technical Process Behind a Drupal to WordPress Migration&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://migratecontent.com/content-migration-process/"&gt;How the migration process works&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;section class="breakout-white"&gt;
&lt;div class="breakout-inner text-center"&gt;

&lt;h2&gt;Ready to Start Planning Your Migration?&lt;/h2&gt;

&lt;p&gt;Send me a brief overview of your Drupal site and I'll provide a free initial assessment: what's involved, what to expect, and a ballpark timeline for your specific situation.&lt;/p&gt;

&lt;div class="button-container" style="margin:2em 0;"&gt;
&lt;a class="cta-button" href="https://migratecontent.com/contact/" title="Get a free migration assessment"&gt;Get a Free Quote&lt;/a&gt;
&lt;/div&gt;

&lt;/div&gt;
&lt;/section&gt;</description><category>drupal</category><category>migration</category><category>planning</category><category>preparation</category><category>wordpress</category><guid>https://migratecontent.com/how-to-prepare-drupal-wordpress-migration/</guid><pubDate>Mon, 02 May 2016 10:05:59 GMT</pubDate></item><item><title>Drupal to WordPress migration worksheet</title><link>https://migratecontent.com/drupal-wordpress-migration-worksheet/</link><dc:creator>Anthony Lopez-Vito</dc:creator><description>&lt;p&gt;If you are using my Drupal to WordPress Migration Tool or have hired me for &lt;a href="https://migratecontent.com/drupal-to-wordpress-migration-service/" title="Drupal to WordPress migration service"&gt;Drupal to WordPress migration service&lt;/a&gt;, it's important that you gather as much information as you can about your Drupal installation. The more detailed you are in your investigation, the fewer surprises there will be during the actual migration. You may have hired a web development company or freelancer to build your site and they'll sometimes be able to provide you with the necessary information. However, gathering this information can involve some work so they may be reluctant to provide help without an extra fee.&lt;/p&gt;
&lt;p&gt;You can use the questions below to help structure your investigation process. I can help you with this if you're not able to run the investigation yourself. &lt;a href="https://migratecontent.com/contact/"&gt;Please ask for details&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;Drupal Installation Questions&lt;/h2&gt;

&lt;em&gt;What are the FTP login details of your hosting provider?&lt;/em&gt;You will need these details to make a backup of your Drupal site. When the migration is complete, you'll need them to install WordPress on your server.


	&lt;table style="width: 100%"&gt;
&lt;caption&gt;FTP Credentials&lt;/caption&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;th style="width: 30%"&gt;
	Host&lt;/th&gt;
&lt;td style="width: 70%"&gt;
 &lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;th&gt;
	Port&lt;/th&gt;
&lt;td&gt; &lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;th&gt;
	Protocol&lt;/th&gt;
&lt;td&gt; &lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;th&gt;
	Username&lt;/th&gt;
&lt;td&gt; &lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;th&gt;
	Password&lt;/th&gt;
&lt;td style="color:#aaa"&gt;Send through secure channel e.g. password manager&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;


&lt;em&gt;What are the database login details of your hosting provider?&lt;/em&gt;You'll need these to export your Drupal database to perform the migration.

&lt;table style="width: 100%"&gt;
&lt;caption&gt;Database Credentials&lt;/caption&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;th style="width: 30%"&gt;
	Host&lt;/th&gt;
&lt;td style="width: 70%"&gt;
 &lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;th&gt;
	Port&lt;/th&gt;
&lt;td&gt; &lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;th&gt;
	Database name&lt;/th&gt;
&lt;td&gt; &lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;th&gt;
	Username&lt;/th&gt;
&lt;td&gt; &lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;th&gt;
	Password&lt;/th&gt;
&lt;td style="color:#aaa"&gt;Send through secure channel e.g. password manager&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;

&lt;em&gt;Do you know how to export your database to a dumpfile?&lt;/em&gt;If you're unsure how to export your database to a 'dumpfile', please contact your hosting provider. They will likely have tools such as phpMyAdmin and help articles to guide you through the process.&lt;br&gt;
&lt;table style="width: 100%"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;th style="width:90%"&gt;
	 &lt;/th&gt;
&lt;td style="width:10%; text-align:center"&gt;&lt;strong&gt;Yes/No&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;th style="width:90%"&gt;
	I know how to export my database to a dump file&lt;/th&gt;
&lt;td style="width:10%"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;th&gt;
	I need help exporting my database to a dump file&lt;/th&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;div class="page-break"&gt;&lt;/div&gt;

&lt;em&gt;What version of Drupal are you running?&lt;/em&gt;The database column names differ slightly between Drupal versions. This means that a different set MySQL queries will be needed to perform the migration. You can sometimes find this information using your installation's &lt;em&gt;CHANGELOG&lt;/em&gt; file at http://[YOURDOMAIN.COM]/CHANGELOG.txt. Some developers remove this file as part of their security hardening process so it may not exist in your installation.&lt;br&gt;
&lt;table style="width: 100%"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;th style="width:90%"&gt;
	Drupal version&lt;/th&gt;
&lt;td style="width:10%"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;

&lt;em&gt;List your Drupal modules and site functionality&lt;/em&gt;Can the functionality can be handled with existing WordPress plugins? Will you need to develop custom plugins?&lt;br&gt;
&lt;table style="width: 100%"&gt;
&lt;caption&gt;Drupal modules and functionality&lt;/caption&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="height: 200px"&gt;
 &lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;

&lt;em&gt;How many custom content types do you have set up?&lt;/em&gt;Additional migration MySQL queries will be needed for each Drupal custom content type. WordPress supports &lt;em&gt;page&lt;/em&gt; and &lt;em&gt;post&lt;/em&gt; content types as standard. Additional development work will be needed to support other content types.&lt;br&gt;
&lt;table style="width: 100%"&gt;
&lt;caption&gt;Drupal custom content types&lt;/caption&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="height: 200px"&gt;
 &lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;div class="page-break"&gt;&lt;/div&gt;

&lt;em&gt;How many custom fields do you have set up?&lt;/em&gt;As with custom content types, custom fields in your Drupal installation will need additional work to support them under WordPress.&lt;br&gt;
&lt;table style="width: 100%"&gt;
&lt;caption&gt;Drupal custom fields&lt;/caption&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="height: 200px"&gt;
 &lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;

&lt;em&gt;Do you have blocks, views and panes with important content?&lt;/em&gt;Many Drupal sites display content in blocks, views and panes. These will also need additional work to support under WordPress.&lt;br&gt;
&lt;table style="width: 100%"&gt;
&lt;caption&gt;Drupal blocks, views and panes&lt;/caption&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="height: 200px"&gt;
 &lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;

&lt;em&gt;How many nodes do you have?&lt;/em&gt;The number of Drupal nodes you have does not usually play a big factor in the complexity of the migration. However, it will still be useful to get an idea of the number since many nodes can have an impact on how long it takes to troubleshoot migration problems.&lt;br&gt;
&lt;table style="width: 100%"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;th style="width:90%"&gt;
	Approximate number of Drupal nodes&lt;/th&gt;
&lt;td style="width:10%"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;div class="page-break"&gt;&lt;/div&gt;

&lt;em&gt;Do you expect to have multiple aliases referencing the same post?&lt;/em&gt;Drupal supports multiple URL aliases for nodes. These will need to be resolved when migrating to WordPress. For more information, please see my article &lt;a href="https://migratecontent.com/preserving-seo-drupal-wordpress-migration/" title="Preserving SEO during a Drupal to WordPress migration"&gt;Preserving SEO during a Drupal to WordPress migration&lt;/a&gt;.&lt;br&gt;
&lt;table style="width: 100%"&gt;
&lt;caption&gt;Brief description of what to do with multiple aliases&lt;/caption&gt;
&lt;tfoot&gt;
&lt;tr&gt;
&lt;td style="border:none;"&gt;
		&lt;em&gt;It's OK if you don't know. We can discuss your options.&lt;/em&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tfoot&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="height: 200px"&gt;
 &lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;

&lt;em&gt;Do you expect to have duplicate terms?&lt;/em&gt;Duplicate Drupal terms can cause problems during a migration. Handling Drupal terms during a Drupal to WordPress migration requires careful planning to avoid data loss.&lt;br&gt;
&lt;table style="width: 100%"&gt;
&lt;caption&gt;Brief description of what to do with duplicate terms&lt;/caption&gt;
&lt;tfoot&gt;
&lt;tr&gt;
&lt;td style="border:none;"&gt;
		&lt;em&gt;It's OK if you don't know. We can discuss your options.&lt;/em&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tfoot&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="height: 200px"&gt;
 &lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;div class="page-break"&gt;&lt;/div&gt;

&lt;em&gt;Will your terms exceed the WordPress' 200 character length?&lt;/em&gt;WordPress has a 200 character limit for terms. Any Drupal terms longer than 200 characters will need to be truncated.&lt;br&gt;
&lt;table style="width: 100%"&gt;
&lt;caption&gt;Brief description of what to do with problem terms&lt;/caption&gt;
&lt;tfoot&gt;
&lt;tr&gt;
&lt;td style="border:none;"&gt;
		&lt;em&gt;It's OK if you don't know. We can discuss your options.&lt;/em&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tfoot&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="height: 200px"&gt;
 &lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;

&lt;em&gt;How many users do you have?&lt;/em&gt;The number of users doesn't play a big factor during a migration but it may be useful to know.&lt;br&gt;
&lt;table style="width: 100%"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;th style="width:90%"&gt;
	Approximate number of users&lt;/th&gt;
&lt;td style="width:10%"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;

&lt;em&gt;How many user roles do you have?&lt;/em&gt;Your Drupal user roles may need to be converted into &lt;a href="https://codex.wordpress.org/Roles_and_Capabilities" title="WordPress Roles and Capabilities"&gt;WordPress roles&lt;/a&gt;.&lt;br&gt;
&lt;table style="width: 100%"&gt;
&lt;caption&gt;List and brief description of user roles&lt;/caption&gt;
&lt;tfoot&gt;
&lt;tr&gt;
&lt;td style="border:none;"&gt;
		&lt;em&gt;It's OK if you don't know. We can discuss your options.&lt;/em&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tfoot&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="height: 200px;"&gt; &lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;


&lt;div class="page-break"&gt;&lt;/div&gt;
&lt;h2&gt;WordPress Installation Questions&lt;/h2&gt;

&lt;em&gt;Will preserving SEO be an important part of the project?&lt;/em&gt;For more information, please see my article &lt;a href="https://migratecontent.com/preserving-seo-drupal-wordpress-migration/" title="Preserving SEO during a Drupal to WordPress migration"&gt;Preserving SEO during a Drupal to WordPress migration&lt;/a&gt;.&lt;br&gt;
&lt;table style="width: 100%"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;th style="width:90%"&gt;
	 &lt;/th&gt;
&lt;td style="width:10%; text-align:center"&gt;&lt;strong&gt;Yes/No&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;th style="width:90%"&gt;
	Preserving SEO is important for this project&lt;/th&gt;
&lt;td style="width:10%"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;

&lt;em&gt;Aside from migrating to WordPress, do you also plan to redesign the site?&lt;/em&gt;Redesigning the site will obviously involve more work as it will require a custom WordPress theme. Some site owners are happy to use a free or premium off-the-shelf theme template.&lt;br&gt;
&lt;table style="width: 100%"&gt;
&lt;caption&gt;Ideas for the WordPress theme&lt;/caption&gt;
&lt;tfoot&gt;
&lt;tr&gt;
&lt;td style="border:none;"&gt;
		&lt;em&gt;e.g. list the names, URLs and prices of any pre-made template candidates&lt;/em&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tfoot&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="height: 200px"&gt;
 &lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;

&lt;em&gt;Are there existing WordPress plugins that match your Drupal functionality?&lt;/em&gt;If you're happy to be flexible, you may find WordPress plugins that closely match any Drupal modules you have installed on your existing site. Set aside some time to search the &lt;a href="https://wordpress.org/plugins/" title="WordPress Plugin Directory"&gt;WordPress Plugin Directory&lt;/a&gt;. If you don't find anything suitable, you may have to consider setting aside some budget for custom plugin development.&lt;br&gt;
&lt;table style="width: 100%"&gt;
&lt;caption&gt;List some possible WordPress plugins you may have found&lt;/caption&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="height: 200px"&gt;
 &lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;


&lt;section class="breakout-white"&gt;
&lt;div class="breakout-inner text-center"&gt;

&lt;h2&gt;Need Help Preparing Your Migration?&lt;/h2&gt;

&lt;p&gt;I specialise in complex Drupal to WordPress migrations. If you need help completing this worksheet or planning your migration project, get in touch for a free, no-obligation consultation.&lt;/p&gt;

&lt;div class="button-container" style="margin:2em 0;"&gt;
&lt;a class="cta-button" href="https://migratecontent.com/contact/" title="Get a quote for your Drupal to WordPress migration"&gt;Get a Free Quote&lt;/a&gt;
&lt;/div&gt;

&lt;/div&gt;
&lt;/section&gt;</description><category>drupal</category><category>migration</category><category>planning</category><category>wordpress</category><guid>https://migratecontent.com/drupal-wordpress-migration-worksheet/</guid><pubDate>Mon, 25 Apr 2016 00:00:14 GMT</pubDate></item></channel></rss>