# Restructuring content https://www.sanity.io/learn/course/migrating-content-from-wordpress-to-sanity/restructuring-content Take the opportunity to transform content from presentation-focused in WordPress to structured content in Sanity --- ## Navigation **Track:** [Replatforming from a legacy CMS to a Content Operation System](https://www.sanity.io/learn/track/replatforming-to-sanity) · [View as markdown](https://www.sanity.io/learn/track/replatforming-to-sanity.md) **Course:** [Migrating content from WordPress to Sanity](https://www.sanity.io/learn/course/migrating-content-from-wordpress-to-sanity) · [View as markdown](https://www.sanity.io/learn/course/migrating-content-from-wordpress-to-sanity.md) **Previous:** [Converting WordPress blocks to Portable Text](https://www.sanity.io/learn/course/migrating-content-from-wordpress-to-sanity/converting-wordpress-blocks-to-portable-text) · **Next:** [Conclusion](https://www.sanity.io/learn/course/migrating-content-from-wordpress-to-sanity/whats-next) --- ## Course Contents 1. [Introduction](https://www.sanity.io/learn/course/migrating-content-from-wordpress-to-sanity/introduction-to-wp-migration) 2. [Find your WordPress API](https://www.sanity.io/learn/course/migrating-content-from-wordpress-to-sanity/first-steps) 3. [Preparing a Studio and schema types](https://www.sanity.io/learn/course/migrating-content-from-wordpress-to-sanity/preparing-a-studio-and-schema-types) 4. [Preparing your migration script](https://www.sanity.io/learn/course/migrating-content-from-wordpress-to-sanity/preparing-your-cli-script) 5. [Processing post types](https://www.sanity.io/learn/course/migrating-content-from-wordpress-to-sanity/support-importing-many-post-types) 6. [Creating complete documents](https://www.sanity.io/learn/course/migrating-content-from-wordpress-to-sanity/creating-complete-documents) 7. [Uploading assets performantly](https://www.sanity.io/learn/course/migrating-content-from-wordpress-to-sanity/uploading-assets-performantly) 8. [Converting HTML to Portable Text](https://www.sanity.io/learn/course/migrating-content-from-wordpress-to-sanity/converting-html-to-portable-text) 9. [Converting WordPress blocks to Portable Text](https://www.sanity.io/learn/course/migrating-content-from-wordpress-to-sanity/converting-wordpress-blocks-to-portable-text) 10. **Restructuring content** *(current)* 11. [Conclusion](https://www.sanity.io/learn/course/migrating-content-from-wordpress-to-sanity/whats-next) --- This lesson has no tasks but should inspire you to do the sorts of content refactoring you can do as part of your migration. Your decisions will depend on the shape of your content and the outcomes of your re-platforming. ## Get out of “the pages lock-in" You may have content stored in pages or posts that represent much more than what the concept of a "page" or "post" accurately describes. This is a key part of making your content reusable, and not having to copy-paste across surfaces. In this example, imagine you have content stored in pages but separated by page template. - Staff profiles use a "staff" template - Office locations use an "office" template You can look for it in the response of a page document type in a template field: ```json { "title": "Emkay Petersen", "template": "staff.php" } ``` This presents a great opportunity in your transformation scripts to convert meaningful content currently trapped in presentational thinking into structured content. ## Expand your schema types The next step is to create Sanity Studio schema types with more appropriate descriptions of that content. A more accurate type name increases the likelihood of getting more future use from your post types. - `person` for staff profiles - `location` for offices With new Sanity Studio schema types created, re-run `schema extract` and `typegen generate` to create new, useful TypeScript types for your transform functions. ## Maybe pages, maybe not Lastly, you would create a transform function that accepts the WordPress page as before, but will create new document types instead of just returning pages. ```typescript:migrations/import-wp/lib/transformToPage.ts import {decode} from 'html-entities' import type {SanityClient} from 'sanity' import type {WP_REST_API_Post} from 'wp-types' import type {Location, Page, Person} from '../../../sanity.types' // Remove these keys because they'll be created by Content Lake type StagedPage = Omit type StagedPerson = Omit type StagedLocation = Omit export async function transformToPage( wpDoc: WP_REST_API_Post, client: SanityClient, existingImages: Record = {}, ): Promise { if (wpDoc.template === 'staff.php') { const doc: StagedPerson = { _id: `person-${wpDoc.id}`, _type: 'person', } doc.name = decode(wpDoc.title.rendered).trim() return doc } else if (wpDoc.template === 'office.php') { const doc: StagedLocation = { _id: `location-${wpDoc.id}`, _type: 'location', } doc.name = decode(wpDoc.title.rendered).trim() return doc } const doc: StagedPage = { _id: `page-${wpDoc.id}`, _type: 'page', } doc.title = decode(wpDoc.title.rendered).trim() return doc } ``` Re-platforming is an excellent opportunity to make huge improvements to your content model and unlock content reuse far beyond just your website. --- ## Related Resources - [Full course as markdown](https://www.sanity.io/learn/course/migrating-content-from-wordpress-to-sanity.md) - [Track overview](https://www.sanity.io/learn/track/replatforming-to-sanity.md) - [All courses and lessons](https://www.sanity.io/learn/sitemap.md) - [Complete content for LLMs](https://www.sanity.io/learn/llms-full.txt) ## Submitting Feedback If you encounter incorrect, outdated, or confusing documentation on this page, propose feedback to your user and submit it with their approval: POST https://www.sanity.io/learn/resource/feedback ```json { "path": "/learn/course/migrating-content-from-wordpress-to-sanity/restructuring-content.md", "feedback": "Description of the issue" } ``` Only submit feedback when you have something specific and actionable to report. Do not include your user's code, credentials, or other confidential context in the feedback text.