Amazon’s closure FAQ confirms that Mechanical Turk ends on September 30, 2026. Submission, settlement and historical records do not share one deadline. A workflow that only stops creating new tasks can still leave unfinished administrative work.
Use the official timetable
The MTurk closure FAQ sets September 30 as the submission cutoff, October 30 as the bonus deadline and the end of the post-closure approval window, and January 28, 2027 as the transaction-history access limit. Review the FAQ for the handling of individual pending assignments and payment schedules.
For SageMaker Ground Truth and Amazon Augmented AI, the FAQ specifically describes removal of the Mechanical Turk worker type. This is not an announcement that every workforce option in those products is closing.
Inventory tasks by state
An original migration worksheet can use four columns: task identifier, submission state, review state and payment or bonus state. Keep the fields separate. A task submitted by a worker can still be awaiting review; a reviewed task can still need a separately planned bonus.
For example, imagine a batch with 100 assignments: 70 reviewed, 20 submitted but not reviewed, and 10 not submitted. Those categories add to 100, but only the first 90 contain submitted work. Treating all 100 as “pending” hides the difference between work to review and work that has not arrived. These figures are illustrative, not a real MTurk account.
Check the live account's individual deadlines against the FAQ. Do not interpret the outer October date as permission to postpone every assignment until that day.
Preserve context with the results
An export is more useful when it includes the task instructions and the version of the form workers saw, alongside answers and your review decisions. Otherwise a replacement system may receive labels without the question that gave them meaning.
For a workflow migration, rehearse a small sample from creation through submission, review and downstream import. Compare the returned fields with what the existing application expects. Decide explicitly how incomplete work is represented instead of silently converting a missing answer into a negative label.
Workers should follow the FAQ's payment-preference instructions in their own portal; requesters should reconcile the task and payment states relevant to their account. PeopleAreGeek has not accessed an MTurk account or performed a migration. This article provides a way to organize the closure work around the published dates.
Replace relative countdown with official closure, approval and history dates; distinguish MTurk workforce from all Ground Truth services.