Create a migrate tips function

[rohitpaulk]

For #3399, includes #3420

[chadwhitacre]

!m @rohitpaulk

[chadwhitacre]

Once #3415 settles down let's figure out how to merge #3399 (comment) and this.

[chadwhitacre]

Rebased on master.

[chadwhitacre]

I would leave this out and let mtime be set to now. No?

[rohitpaulk]

Hmm, I'm not sure. We use mtime to show when the tip was last modified in the UI (Last set). Do we want that to be the time when the user last set it, or the time when we migrated the tip?

[chadwhitacre]

I suppose we want to run this when we approve a team for the first time.

[chadwhitacre]

How does this compare with the SQL I used the other day?

#3399 (comment)

[rohitpaulk]

How does this compare with the SQL I used the other day?

That excludes tips from suspicious/closed/unclaimed accounts and also checks for amount > 0. Makes sense to exclude those here too.

[rohitpaulk]

I suppose we want to run this when we approve a team for the first time.

Should we also send the tippers (subscribers, now) a notification?

[chadwhitacre]

@rohitpaulk Yes, definitely. Good call.

[chadwhitacre]

We should go back and notify the new subscribers from last week as well.

[rohitpaulk]

Rebased on master.

[rohitpaulk]

@whit537 - I'm going to use this for #3486 (comment), can you have a look and merge it in?

[chadwhitacre]

Yes, just reread it, looks good. Go ahead and merge once Travis runs green.

[rohitpaulk]

Deploying...

[rohitpaulk]

Deployed.

[chadwhitacre]

Awesome. Now to call it for the users in question?

[rohitpaulk]

I tested this on a backup, I can confirm that tips are migrated and an error is raised if the migration is attempted twice.

[rohitpaulk]

Now to call it for the users in question?

Yep. Heading back to #3486...