Alright so here's the plan
1. Double check anomaly and sheriff configs to make sure the alert paths don't need changed
2. Hit submit on https://codereview.chromium.org/2907643002/
3. Wait for new data to show up on perf dashboard
4. Kick off the migrations for each test path (full list here: https://docs.google.com/a/google.com/spreadsheets/d/1KauoMh6znQLj_gQDMtP3we924LFagIeL-GervMW8TyI/edit?usp=sharing)

Does anyone have questions or concerns about this plan of action?

LGTM

lgtm

Looking like none of the anomaly or sheriff configs have any loading.mobile stories hardcoded so no changes should be needed there
Hitting submit now

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/aead6369dea3e206264040f71d66415af55d47b8

commit aead6369dea3e206264040f71d66415af55d47b8
Author: ashleymarie <ashleymarie@chromium.org>
Date: Wed May 31 20:23:10 2017

Explicitly setting story names for the loading_mobile story set.

BUG= chromium:720002 
BUG= chromium:728006 

Review-Url: https://codereview.chromium.org/2907643002
Cr-Commit-Position: refs/heads/master@{#475998}

[modify] https://crrev.com/aead6369dea3e206264040f71d66415af55d47b8/tools/perf/page_sets/loading_mobile.py

Patchset committed; now waiting on the first round of data to show up on the perf dashboard so I can begin migrations!

Data has started showing up! I'm gonna give it a few more hours before kicking off the migrations

Looking good on the dashboard
Starting migrations!

migration completed a few days ago successfully; just forgot to close the bug