SyncPort — Migration & Sync
Selectively migrate WordPress content, settings, media, and database tables between connected sites.
★ 0stars
21composer installs
0forks
Install
No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:
wp plugin install https://github.com/justdev-studio/syncport/archive/refs/heads/develop.zipAlso on Packagist as justdev/syncport:
composer require justdev/syncportFrom the readme
SyncPort — Migration & Sync
SyncPort migrates selected WordPress data between separately installed WordPress sites. It is a modern, modular successor to the bundled jd-wp-sync-db-master and jd-wp-sync-db-media-files-master references.
Requirements
- WordPress 6.4 through 7.x
- PHP 8.1 through 8.4
- MySQL 5.7+ or MariaDB 10.4+
- HTTPS for production connections
- The same major SyncPort protocol version on connected sites
There is no frontend build step.
Composer installation
The package uses Composer's wordpress-plugin installer type and is installed into the WordPress plugins directory through composer/installers:
For a private VCS package, add its repository to the root project before running the command. The installer directory name is fixed to syncport.
Product rules
- Every migration has one source and one or more independently analyzed targets.
- Push may target multiple sites. Pull has one source per operation.
- A preflight is required before writes.
- Existing entities are matched by SyncPort UUID, then offered as a possible match by post type and slug.
- A changed match is a conflict. The user must replace, skip, or create a duplicate.
- A selected entity include