Platform › Legacy Migration
Migration Resets
Every time a company’s cutover was started again, and what it took with it. Kept because the load runs a reset deletes were what accounted for records that now exist — so this is the only trace a wipe leaves.
Where to find it
- Module: Platform
- Group: Operations
- Section: Legacy Migration
- Screen: Migration Resets
Address in the console: /platform/migration-resets
Read-only list · 9 columns
This list is read-only: its records are written by the work that produces them. A correction, where one is possible at all, is made where the record was created.
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Reset At | Date | reset_at |
| By | Text | reset_by_name |
| Scope | Status | scope |
| Batches | Number | batches |
| Rows | Number | records |
| Runs | Number | runs |
| Removed | Number | removed |
| Refused | Number | refused |
| Summary | Text | summary |
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.