SleekView for Migrate Guru: migration jobs & logs as tables
Migrate Guru runs migrations through BlogVault's hosted infrastructure, with each job's state mirrored to wp_options. SleekView reads that mirror as a filterable status board across every job ever run on the site.
♾️ Lifetime License available
Job history that doesn't disappear into the cloud
Migrate Guru's value proposition is that migrations run on BlogVault's servers rather than tying up the source site. The trade-off is that the operational history lives partly in BlogVault's cloud dashboard. The WordPress side mirrors job state, target host, source URL, current progress, and outcome to wp_options entries the plugin writes during a migration.
SleekView surfaces that local mirror as a sortable inventory. Each job row exposes start date, source URL, target host, target URL, status (queued, running, complete, failed), duration, and any error message. A view filtered to status = failed surfaces every botched migration in one screen. Filtering to duration > 30 minutes highlights the jobs that ran slow and are worth post-mortem.
For agencies running migrations across many client sites, the same view pattern can be aggregated network-wide so the lead engineer audits the whole pipeline from one workspace. Capability gating keeps target hostnames and credential references visible only to roles that should see them.
Workflow
Read Migrate Guru's local mirror as a status board
Map the wp_options mirror
Filter the failed cohort
Sort by duration
Capability-gate target hostnames
Sample columns
A typical Migrate Guru jobs view
wp_options entries.
wp_options (migrateguru_*) + job log
| Started | Source | Target | Duration | Outcome | Job ID |
|---|---|---|---|---|---|
| Apr 24 03:12 | site.com | newhost.com | 18 min | Complete | MG-401923 |
| Apr 23 14:01 | client.io | newhost.com | 42 min | Complete | MG-401922 |
| Apr 22 09:47 | store.shop | newhost.com | — | Queued | MG-401910 |
| Apr 12 22:31 | blog.dev | newhost.com | 9 min | Failed | MG-401865 |
Comparison
Default Migrate Guru admin vs SleekView
Default Migrate Guru admin
- Job state is shown for the in-progress migration with limited history visibility
- Cross-job audits ("every failed migration this month") need bouncing to BlogVault's dashboard
- Duration and outcome aren't a sortable, filterable column set on the WP side
- Network-wide aggregation across client sites isn't a built-in view
- Failed-job triage requires opening each job individually
SleekView
-
Read Migrate Guru's
wp_optionsjob mirror directly - Sort and filter by start date, duration, source/target, and outcome
- Surface failed-job cohort as a saved filter for post-mortem
- Capability-gate target hostnames so only ops roles see them
- Aggregate network-wide for agencies running many concurrent migrations
Features
What SleekView gives you for Migrate Guru
Job history at a glance
Every migration job ever run on the site in one ranked list with start date, source, target, duration, and outcome. Cross-job audits stop requiring cloud-dashboard context switches.
Failed-job triage
Filter to outcome = failed across the entire job history. Each row exposes the error message inline so post-mortem starts with the actual cause, not a hunt through cloud logs.
Duration outliers
Sort by duration descending to surface the jobs that ran slow. Cross-reference with target host to spot infrastructure issues that affect multiple migrations to the same destination.
Audience
Who uses SleekView for Migrate Guru
Migration ops
One workspace covering every job's state and outcome. Failed migrations triage from a saved filter; long-running jobs surface from a duration sort. Replaces cloud-dashboard bouncing during incident response.
Audit & compliance
Queryable record of every migration the site has ever performed, with source, target, and outcome. Regulatory audits answer "when did we move customer X's data" without leaving WP admin.
Agency leads
Network-wide aggregation of jobs across client sites so the lead engineer reviews the whole pipeline from one workspace. Capability gating keeps individual client hostnames scoped per role.
The bigger picture
Why cloud-driven migrations still need a local audit layer
Migrate Guru's design moves the heavy lifting off the source site and onto BlogVault's infrastructure, which is exactly the right call for migrations of large WooCommerce stores or multisites where a self-hosted migration would be too slow or too disruptive. The trade-off is that the operational truth lives partly in BlogVault's cloud dashboard, and the WordPress side is left with a mirror of recent job state. For day-to-day ops that mirror is enough as long as it's actually queryable.
Reading the wp_options entries Migrate Guru writes locally turns the WordPress half of the story into a real audit layer. Failed-job triage becomes a saved filter; cross-job duration analysis becomes a sort; agency-scale review across many client sites becomes a network-wide aggregate. The cloud dashboard remains the right place for the full transfer log, and SleekView's view is honest about that scope.
What it adds is the queryable WordPress-side history that compliance, post-mortem, and concurrent-migration triage all need without leaving WP admin or context-switching to a separate dashboard mid-incident.
Questions
Common questions about SleekView for Migrate Guru
The plugin's wp_options entries that mirror job state during and after a migration, plus any local job log records the plugin maintains. The full migration logs live in BlogVault's cloud dashboard; SleekView surfaces what the plugin writes locally.
Migrate Guru itself requires a BlogVault account to run migrations because the actual transfer happens on BlogVault's infrastructure. SleekView reads the WordPress-side records that the plugin maintains regardless of whether you're actively logged in to BlogVault during the audit.
Migration kickoff happens through the plugin's own UI because it negotiates the BlogVault-side job. The SleekView job-history view is for audit, triage, and post-mortem. Inline-edit on the local mirror records is limited to annotations rather than control actions.
Filter to outcome = failed across the entire history. Each row exposes the error message the plugin wrote locally and a link out to the corresponding BlogVault cloud-side log entry where the full transfer detail lives. The combination of local audit and cloud detail covers most post-mortems.
Yes. Jobs in queued or running states surface in the same view, with progress percent and elapsed time as columns. The view auto-refreshes when configured to so on-call engineers watch active migrations from the WordPress side without keeping the BlogVault dashboard open.
Yes. On a multisite or for an agency managing many independent client sites, the job-history view can be aggregated network-wide where the relevant plugin and capabilities exist. The lead engineer reviews every client's recent migrations from one workspace.
Yes. Target hostnames and credentials references are sensitive, so the view defaults to administrator and migration-ops capability. Other roles do not see the job-history at all unless granted access explicitly.
Migrate Guru's primary role is migration rather than backup-restore. Where the plugin writes restoration records to the same wp_options mirror, the view exposes them as their own status filter, but BlogVault's broader restore tooling lives in their dedicated product.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout