# Pulling changes from WordPress

A pull brings the current WordPress version of a post into its linked Workover document. Use it when the post was changed in WordPress and you want those changes in Workover before you edit or push again.

**Before you start:** the document must be linked to a WordPress post. Pull is always available on a linked document, in the **WP** tab.

> **Warning:** A pull replaces the document’s body and WordPress fields with what is on WordPress, and discards edits you have not pushed. Version history saves automatically at most once every 10 minutes, so it may not hold your latest edits from before the pull. Copy anything you want to keep, or push it first.

## When to pull

- The **WP** tab says **New changes in WordPress**, or the document list shows a **WordPress update** pill: someone edited the post in WordPress, or a plugin changed it.
- Workover stopped a push because the post changed in WordPress, and you want to see those changes before deciding.
- You want an imported document refreshed from the current post.

## Pull a post

1. Open the document and select the **WP** tab in the side panel. If it says **Another tab is linked to WordPress**, select **Go to the WordPress tab**.
2. Select **Pull**. When WordPress has newer changes, **Pull** is the highlighted button.
3. In **Pull the latest version from WordPress?**, select **Pull latest**.

The document now matches the post, and the status at the top of the tab updates to match. Reapply any edits you still need, then [push](/docs/pushing-to-wordpress/).

## What a pull replaces

| Replaced with the WordPress version | Not touched |
| --- | --- |
| The body of the tab that syncs to WordPress | Your document’s other [tabs](/docs/document-tabs/) |
| The title |  |
| The workflow status, which follows the post’s WordPress status |  |
| The publication date |  |
| WordPress field edits you staged but have not pushed (they are discarded) |  |

Workover also records the post’s current modification time, which is what clears **New changes in WordPress**.

When the site lets Workover read a post’s block markup, custom blocks, ACF blocks and shortcodes come back as blocks Workover carries through unchanged. Otherwise the post’s rendered HTML is used, and those blocks are flattened. See [Custom blocks and ACF fields](/docs/custom-blocks-and-acf/).

## Pull first, or overwrite?

If a push was stopped because the post changed in WordPress, you can pull first or overwrite the WordPress changes. [How to fix a push to WordPress that failed](/docs/push-failures/) helps you choose. If you cannot tell whether the WordPress change matters, open the post in WordPress and look before you decide.

## Related

- [How WordPress sync works](/docs/how-wordpress-sync-works/)
- [Sync status and conflicts](/docs/sync-status-and-conflicts/)
- [How to push a document to WordPress](/docs/pushing-to-wordpress/)
- [Version history](/docs/version-history/)