

Select content filters and portable dependencies on the Export tab.
Sadat Content Migration is a selective WordPress content migration tool. It moves the content you choose and its portable dependencies without cloning themes, plugins, users, database tables, or the entire website.
Use it when you need to transfer blog posts, move pages between environments, copy a custom post type, or hand a controlled content package to another WordPress administrator.
The plugin transfers portable post and term metadata, including metadata keys commonly used by Yoast SEO, Rank Math, SEOPress, The SEO Framework, and similar plugins. Vendor-specific custom database tables, global plugin options, redirects, and analytics data are not migrated. Install and configure the same SEO plugin on the destination before importing when you need its fields to be interpreted there.
Sadat Content Migration does not collect analytics, add tracking, or contact the developer’s website. Migration packages can contain private content or personal data if an administrator selects those options. Treat downloaded packages as confidential and delete them when the migration is complete.
Temporary packages and processing files are stored below the current site’s WordPress uploads directory, in sadat-content-migration/site-ID/, and removed according to the retention setting. Fixed Apache and IIS deny rules protect this directory. Before a job starts, the plugin checks a harmless random text file through the site’s uploads URL and requires an HTTP 403 or 404 response. A successful check is cached for five minutes. If protection cannot be verified, the job does not start. Imported content receives private source identifiers used only for duplicate detection and later updates.
The plugin has no third-party service dependency. It makes a loopback request to its own harmless storage probe to verify that migration files cannot be downloaded directly; no content or personal data is included in this request.
When an administrator starts a direct transfer, the source site contacts only the destination WordPress URL entered by that administrator. It sends package metadata and the selected migration ZIP in sequential chunks to the Sadat Content Migration REST endpoints on that destination. The request uses the short-lived connection key generated by the destination administrator. Nothing is sent until both administrators take those explicit actions.