✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Kanban for All-in-One WP Migration Unlimited

All-in-One WP Migration Unlimited stores every migration job as a row in ai1wm_exports with state, source, and destination. SleekView Kanban reads that data, groups migration jobs by status, and lets the team drag a failed card back to prepared without leaving the admin.

♾️ Lifetime License available

SleekView Kanban board for All-in-One WP Migration Unlimited

Why All-in-One Unlimited migration jobs fit a kanban view

All-in-One WP Migration Unlimited keeps every migration job as a row in ai1wm_exports with the state, the source, the destination, and the runtime stored alongside the slot. Related metadata lives in ai1wm_imports. The default admin screen shows that data as a flat list sorted by date, which is fine for record lookup but slow when an overnight migration job has stalled and a site migration lead needs to see whether it is prepared, running, or has actually moved to failed state.

SleekView Kanban points at the same migration job records and renders them as four columns: Prepared, Running, Completed, and Failed. Each card surfaces the migration job label, the destination handle, and the runtime. When a failed migration job needs another attempt, the team drags the card back into prepared and All-in-One WP Migration Unlimited picks it up on the next pass. No second list, no manual retry through a settings screen that buries the action behind tabs.

The team can filter the board by destination, schedule, or scope, then save that filtered view as a board for one site or one client. The kanban reads from the live migration job records, so retrying a card here triggers the same code path that the standard run button uses, with the same hooks firing for notifications and logs.

Workflow

From All-in-One Unlimited list to a live kanban

1

Connect All-in-One Unlimited as

Pick All-in-One WP Migration Unlimited from the SleekView data source picker. It auto-detects the ai1wm_exports store and the ai1wm_imports metadata so the board reads the same records as the
2

Group cards by the status field

Select the status field as the kanban column. SleekView reads every distinct value, surfaces Prepared, Running, Completed, Failed, and lets the team rename, reorder, hide, or recolor each column without touching the
3

Pick the card front fields

Choose the migration job label, the destination handle, and the runtime as the card front. Add a secondary line for schedule and log line. The card editor previews real migration job data so the team confirms the layout
4

Enable drag-and-drop writeback

Turn writeback on and dragging a card writes the new status back to the All-in-One WP Migration Unlimited record via the WordPress REST API. Capability checks honor the existing admin role, and every move is recorded

Sample board

Sample All-in-One Unlimited board grouped by status

Four real status columns showing how a site migration lead moves All-in-One Unlimited migration jobs across Prepared, Running, Completed, and Failed during a single working session.
Prepared
4
Export full site over 512 MB ready
Estimated 2.4 GB output size
Import staging archive over 512 MB
Source file 2.1 GB archive
Export site without media folder data
Estimated 320 MB output size
Running
1
Exporting full site over 512 MB now
Files 2820 of 6420 processed
Importing staging archive currently
Tables 34 of 64 processed
Exporting site without media currently
Tables 28 of 64 processed
Completed
104
Full site export completed successfully
Size 2.4 GB, 16 min runtime
Staging archive import completed ok
Tables 64, 10 min runtime
Site without media export completed
Size 320 MB, 2 min runtime
Failed
2
Full site export did fail mid-run
Disk write error at runtime
Staging archive import did fail
File checksum mismatch error
Site without media export did fail
Disk write error mid runtime

Comparison

Default All-in-One Unlimited list vs SleekView K

Default Unlimited screen

  • Default screen is a flat sortable list hiding migration job status behind a small pill
  • Updating a migration job status takes three clicks and a full page reload every time
  • No live counts per state, so workload across migration jobs stays hidden from the team
  • Bulk actions cover delete and trash but never bulk status moves across many rows
  • Filtering by destination resets when navigating between pages of migration jobs listing

SleekView Kanban

  • Drag a card from failed to prepared and the status writes back live
  • Column counts update live so the migration lead sees workload without filtering or scrolling
  • Save filtered boards as URLs, one per destination, schedule, or scope across the site
  • Card front maps to the migration job label, destination handle, runtime, and last log line
  • Permissions inherit from All-in-One WP Migration Unlimited roles, no second auth layer to mai

Features

What SleekView Kanban gives you for All-in-One WP Migration Unlimited

Status columns you can rename

All-in-One WP Migration Unlimited ships with Prepared, Running, Completed, Failed as the four core states. Rename them to match the runbook, reorder them to match the flow, and recolor each column so the board makes failed

Drag to rerun not re-trigger

Every card move writes back to the same status field that All-in-One WP Migration Unlimited already reads, so retried migration jobs run through the same pipeline as fresh ones. No second queue, no shadow retry list, no risk of

Filter by destination or scope

Add a secondary filter on the destination handle, the scope, or the schedule slot and SleekView narrows the board to that subset. Ops sees the full board, the migration lead sees one destination, and the manager keeps the

Audience

Where migration leads use the All-in-One Unlimited kanban first

Morning migration triage

Open the board at 9am, scan the failed column for overnight issues, drag failed migration jobs back into prepared, and watch the running column drain as the next pass processes the retries from

Pre-release migration checkpoint

Before a release, fire a manual migration job card, watch it move from prepared to running to completed, then promote the deploy. If the migration job fails, the card stays in failed until the retry

Multi-site capacity view

Filter the board to one client site at a time and watch the running column count as a live capacity gauge. If running stays full while prepared grows, stagger schedules before the queue stalls the

The bigger picture

Why a kanban beats the All-in-One Unlimited screen

All-in-One WP Migration Unlimited is a great migration engine. The records hold the state, the destination map holds the targets, and the schedule slot holds the timing. What it does not give the team is a daily operating picture of which migration jobs are healthy and which are not.

The default screen is a record list, designed to inspect a single migration job, not to triage a column of failed migration jobs at once. The site migration lead ends up keeping a separate sticky note of failed runs or wiring a notification plugin just to know which migration job died overnight while the team slept. A kanban changes the shape of the work.

Instead of asking which migration jobs need attention today, the team sees the answer as soon as the page loads, because every failed migration job is in the failed column and every running one is in the running column. Moving a card writes the new status back to the record, so the picture stays accurate.

Questions

Common questions about SleekView Kanban for All-in-One WP Migration Unlimited

No. The board reads from the same ai1wm_exports store that the plugin already uses. When the team drags a card, SleekView writes the new status back to that store, so there is only one source of truth for every migration job on the site and every All-in-One WP Migration Unlimited hook still fires correctly during th

 

Yes. The column titles are display labels, not the underlying status values. Rename prepared to waiting, failed to broken, or anything else that matches how the team writes incident notes. SleekView stores the rename separately so the data still uses the standard All-in-One WP Migration Unlimited values.

 

SleekView Kanban inherits the All-in-One WP Migration Unlimited capability map. If a user can run a migration job or view the admin screen, they can drag the matching card on the board. If they only have view rights, the board renders in read-only mode and the drag handles stay hidden from each card.

 

Yes. Add a filter on the destination handle or the schedule slot, then save the filtered view as a named board. Each board gets its own URL so one destination board lives next to another, and a single board can stay open on a status monitor without losing the rest.

 

The kanban polls the All-in-One WP Migration Unlimited record store at a configurable interval, with two minutes as the default. New completed and failed entries appear in the matching column within that window. Existing cards refresh in place so dragging a card never loses its position when a sibling updates.

 

Yes. SleekView reads every distinct value in the status field, including the extra states that add-ons register for cloud destinations and remote stores. The team chooses which of those columns to show on the board and hides the rest without removing the underlying data.

 

Yes. The card editor lets the team pick any field stored on the migration job record, including the destination handle, the runtime, and the last log line. A common layout shows the migration job label, destination, and runtime on the front, with the log line visible on hover for the engineer.

 

Yes. The plugins do not conflict because SleekView only reads and writes the same records that All-in-One WP Migration Unlimited already manages. Many teams use the admin screen for one-time setup and configuration, and the kanban for daily triage and retries from across the whole site at once.

 

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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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