Migrate User Overview Pages via Sandbox or Alternative Methods

RobB

We have an interest in using Sandbox to migrate Users' Overview pages. We haven't been able to do it at present. We could move cards into repos and then into pages named for each user. Then return ownership to each user and remove the pages. The number of users and the number of cards involved makes this a less desirable approach.

If this can't be done with Sandbox, what alternatives to automate this or perform their migrations at scale exist?

When doing some backend digging, we discover that each overview page has the same ID. I think it's 1000000 (I may be +/- a zero there). I don't know if this means only one overview page and card ownership determines availability or not. It seems that way. We are using this to explore scripted solutions using Sandbox (both CLI and API). We think we'd need to accomplish the following:

1. Generate an access token for each in both instances.
2. Use access token to create a repository.
3. Add users overview page to repo (now that the token singles out only 1 - 1000000 id)
4. Commit repo.
5. Promote repo.
6. Iterate previous steps for the next user.

Other possibilities we may explore:

If there is only one Overview page, could we migrate that along with all content and then use scripting to change card ownership?

Do we need to leave Sandbox out of this all together and rely on APIs to do the work instead, if possible?

GrantSmith

The Overview is an interesting special page. It is generated based on whomever is logged in so the ID will be the same however the cards that are associated with that specific page are dependent on who you are authenticated as.

You'll likely just need to create several different tokens for the different users and repeat the same process with the different user tokens.

GrantSmith

The Overview is an interesting special page. It is generated based on whomever is logged in so the ID will be the same however the cards that are associated with that specific page are dependent on who you are authenticated as.

You'll likely just need to create several different tokens for the different users and repeat the same process with the different user tokens.