內容簡介
Sadat Content Migration 是一款選擇性 WordPress 內容遷移工具，能夠將您選擇的內容及其可攜帶的依賴項移動，而無需克隆主題、外掛、用戶或整個網站。適合在需要轉移文章、頁面或自定義文章類型時使用。
【主要功能】
• 支援選擇性內容遷移
• 下載及上傳驗證的 ZIP 遷移包
• 直接從一個網站傳送至另一個網站
• 可靠的媒體和文章導入
• SEO 元數據的轉移
• 隱私和數據處理保護
外掛標籤
開發者團隊
原文外掛簡介
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.
Two migration workflows
Download and upload a verified ZIP migration package.
Send a completed package directly from one WordPress site to another with a short-lived, single-use connection key.
Portable content and settings
Posts, pages, and registered custom post types.
Same-type parent items required to preserve hierarchical page or custom-post relationships.
Titles, slugs, content, excerpts, dates, status, parent relationships, menu order, discussion settings, and sticky-post state.
Featured images, attached media, inline media, classic galleries and playlists, and Gutenberg image, gallery, audio, and video references.
Categories, tags, custom taxonomies, ancestor trees, descriptions, and term metadata.
Author mapping by login with a configurable local fallback author.
Portable custom fields and metadata-based SEO settings.
Comments, plus optional comment metadata and personal data when an administrator explicitly selects them.
Optional post passwords when an administrator explicitly selects them.
Reliable imports
Media, post creation, and relationship finalization run in small AJAX batches.
Source-to-destination ID and URL maps repair internal links, media markers, block attributes, featured images, and parent relationships.
Existing migrated content can be updated, skipped, or copied.
Matching media can be reused by source identity or SHA-256 file hash.
Custom post types and taxonomies are imported only when they are registered on the destination.
Package paths, MIME types, file sizes, archive expansion, and SHA-256 hashes are validated before import.
Temporary jobs are isolated, expire automatically, and include administrator-readable logs.
SEO metadata
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.
Privacy and data handling
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.
External services
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.
