> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://help.syncspider.com/sitemap.xml > Use this file to discover available pages before exploring further. > Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash). # How to Export and Import Posts and Users with WordPress This article will guide you in detail on how to export and import **Posts** and **Users** from and to **WordPress**. The first step you need to do is to integrate WordPress. You can find the guide on how to do that on the following [hyperlink](https://syncspider-support.freshdesk.com/en/support/solutions/articles/3000115563-how-to-integrate-wordpress). 1. Exporting Posts From WordPress 2. Exporting Users From WordPress 3. Importing Posts To WordPress 4. Importing Users To WordPress For the first task we will choose WordPress as a source integration and choose Post as an [entity](https://syncspider-support.freshdesk.com/en/support/solutions/articles/3000115865-what-is-an-entity-). ![](https://storage.crisp.chat/users/helpdesk/website/-/a/3/a/8/a3a84907263e4000/2031703f-4036-4ec0-b9b8-7b0ae7_j3z6fa.png) In order to proceed we also need to configure which type of posts we want to export. ![](https://storage.crisp.chat/users/helpdesk/website/-/8/9/2/8/89284f737b51e000/cac8b332-8ab0-40c4-86f0-5a76ff_1cb9uvv.png) There are several types that we can filter in and out: **Posts, Pages, Media, Blocks** and **Products**. For the purpose of this guide we will leave all of them in, therefore selecting **All Post Types.** Next step is selecting the unique identifier **(UID).** Which means that it will be the determinant of the post's unique identification. We can choose between the posts' **Name** and **ID.** ![](https://storage.crisp.chat/users/helpdesk/website/-/8/1/4/c/814cefd07da6e800/4a9e471b-c6f3-426f-9d04-fd0012_l57vjf.png) In this case we will select the **ID**, as the posts' names can sometimes be the same in our case. After configuring the Target integration and Filters, the next step is mapping. When exporting posts from **WordPress** there are following options. ![](https://storage.crisp.chat/users/helpdesk/website/-/c/a/6/0/ca605780fe78380/d02b7b67-ecf4-414c-832b-068bef_g19ben.png) ![](https://storage.crisp.chat/users/helpdesk/website/-/c/b/9/7/cb9773c05e885000/e1cb7803-bd57-4756-ba72-1256b0_3aavpn.png) You can find more information about mapping on the following [hyperlink](https://syncspider-support.freshdesk.com/en/support/solutions/articles/3000115964-mapping). Next, we will focus on exporting **Users** from WordPress. ![](https://storage.crisp.chat/users/helpdesk/website/-/5/f/b/6/5fb6b777beea8c00/61310706-4e4d-4b3b-b25c-c2a6d7_134d6dp.png) First step is configuring Users' Unique Identifier Field **(UID).** You can set any of the listed fields to act as a unique identifier. The fields are following: ![](https://storage.crisp.chat/users/helpdesk/website/-/c/9/c/5/c9c5f3fe5144e000/8be84710-4482-4935-8091-369fab_nrfs9v.png) ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875654/original/rOSVC9bp2KFRETLKpc5nu3lynO3RRxWMcQ.png?1658249696) ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875657/original/wI4VUXjZ2uL3C3jd5fzQ3DfyQPNWGkfFcw.png?1658249696) ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875645/original/DhF-sNmM2FNDyNko85FWS3TWsDijJ5xIKg.png?1658249693) ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875630/original/NqwLGPsWMtaMKbe69mpJ7GU1Fm64rYOOLQ.png?1658249689) Whichever field you choose it will act as an ID. After setting Filters and configuring the Target integration next on the list is mapping. The fields that you are able to map in this case are as follows: ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875646/original/m5xaf7GiMPzgbO7N59KwoexzB7_0Oh3X3A.png?1658249694) ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875670/original/p8K9S7nAiKWDkvFsYHM4H3L0WktNO24onQ.png?1658249697) You can find more information about mapping on the following [hyperlink](https://syncspider-support.freshdesk.com/en/support/solutions/articles/3000115964-mapping). Next, we will focus on importing **Posts** to WordPress. Therefore we will select **WordPress** as a **Target** integration. ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875633/original/M9DzsBBAn3b9khsof5p7Fev2nyGSFFjurg.png?1658249690) After configuring Source Integration and setting Filters we are met with the same configuration window as we had when we were configuring **WordPress Posts** as a Source Integration: ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875666/original/mwUGWEKWz3lKem3VdRVlMNnPJvyklJ86nw.png?1658249696) There are several types that we can filter in and out: **Posts, Pages, Media, Blocks** and **Products**. For the purpose of this guide we will leave all of them in, therefore selecting **All Post Types.** Next step is selecting the unique identifier **(UID).** Which means that it will be the determinant of the post's unique identification. We can choose between the posts' **Name** and **ID.** ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875663/original/BWl50r5DPUhVD47f2QDU6o4MkqPR30TWSg.png?1658249696) In this case we will select the **ID**, as the posts' names can sometimes be the same in our case. After configuring the Target integration and Filters, the next step is mapping. When importing posts to **WordPress** there are following options: ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875649/original/W30le8-1m8I1n-hUJ61zKLNAKlwtj2xE-Q.png?1658249695) ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875672/original/lpMIdxH_h9KQCwPvJV4aaHGqFDxapFb3Kw.png?1658249697) Have in mind that the first two fields: **Content** and **ID**, are required, meaning that you need to map them in order to proceed. Lastly we will focus on importing **Users** to **WordPress.** In this case we need to select WordPress as a Target integration and Entity to **User.** ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875662/original/koIkcPsWr_X04wzQH5VDtU0PoLpaFXWjMg.png?1658249696) After configuring Source Integration and setting Filters we are met with the same configuration window as we had when we were configuring **WordPress Users** as a Source Integration: ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875660/original/cn8Vjg0SDHXMIC6UkN8aJq5av_A-Q1tAdw.png?1658249696) ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875655/original/Pd5-SaZa7b6BAVkZWAcxE-wn41ITlTNULg.png?1658249696) ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875658/original/sHQo2BwTKbRoVl2Lg51ON5cw-uNytfqm6g.png?1658249696) ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875644/original/-eLI86VjMTkDZDda3Yv-OceXnFB7oZCwzw.png?1658249693) ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875650/original/2k16-ePNc_XRdGziD8H8wqMvj4LIv4LsbQ.png?1658249695) After configuring WordPress, as the Target integration, the next step is mapping. When importing **Users** to **WordPress** there are following mapping fields: ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875651/original/PzS0LreoGQJxsbD0NP-xKyYELlEIsJRrWA.png?1658249695) ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875667/original/rbSEUepm0H-d3pynpiBmasOi3Czx5vv4BQ.png?1658249697) ![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/3083875668/original/T4KebYQq1-j8iuSNlh-2-cIRC2-pbnaWgA.png?1658249697) Have in mind that the first four fields: **Username**, **Password,** **Email** and **wordpress::user.id.label**, are required, meaning that you need to map them in order to proceed. --- **WordPress** is just one of the tools we support! To check the list of the tools we support, please click [here.](https://www.syncspider.com/integrations/) If you don't see your favorite tool on our list, please take the time and send us a request [here](https://roadmap.syncspider.com/boards/integrations?sort=cached_votes_up) to create an integration for you OR Up-vote it if it's already on the list :)