Move a user's personal maps into your team - (Team web app) – Scribble Maps Help Portal

What the Migrate Maps page does

Sometimes a person saved maps to their own account before they joined your team. The Migrate Maps page moves those personal maps into a team.

The person has to approve the move first. You send a request, they get an email, and nothing moves until they sign in and approve it.

You open the page from Migrate Maps in the sidebar, under Maps. Only owners and admins can see it. The page header reads Migrate Personal Maps.

Which maps move

Map	Does it move?
A map the person owns that is not in any team	Yes.
A map that already belongs to another team	No. It is left alone.
An archived map	No.
A map someone else owns	No. Only that one person's maps are moved.

All of the person's eligible maps move together. You cannot pick single maps.

Once the maps are in the team, team members can open them under the team's permissions. The move cannot be automatically undone.

Step 1: Send the request

In the sidebar, click Migrate Maps.
In User Email, type the email address of the Scribble Maps user whose maps you want to move.
In Team, pick the team the maps should go to. The list only shows teams you own or administer.
Complete the verification box.
Click Send Migration Request.

A box appears titled Request Sent: "We emailed an approval link to the user. Their personal maps will move to the team only after they sign in and approve."

Sending the request does not move anything.

Step 2: The user approves

The person you named gets an email with an approval link. The link works for 7 days. After that you need to send a new request.

They must be signed in to Scribble Maps as that same email address. A forwarded link will not work for anyone else.

When they open the link they see a page titled Approve Map Migration. It tells them how many maps will move and into which team, and warns that it cannot be automatically undone. They click Approve & Move to finish.

The page then reads Maps Migrated and shows how many maps were moved.

If they had no personal maps, they see No Maps to Migrate instead, and nothing changes. If they open the link again after the move is done, they see Already Migrated.

This is not the same as Block Personal Saving

Both features deal with personal maps, but they do different jobs.

Migrate Maps	Block Personal Saving
Moves maps that already exist.	Changes where future saves go.
One named person at a time.	Everyone on a verified SSO domain.
The person must approve.	A team policy you turn on.
On the Migrate Maps page.	On the Map Security page.

If the request will not send

Message	What to do
Enter a valid email address	Check the address you typed.
Select a team	Pick a team from the dropdown.
Please complete the verification	Finish the verification box, then send again.
You must be an Owner or Admin of a team to migrate maps.	You do not own or administer any team. Ask your team owner.
No Scribble Maps account was found for that email address.	The person needs a Scribble Maps account first. Check for a typo, or ask which address they use.
This team must have an active subscription with at least one non-viewer seat before personal maps can be migrated into it.	Buy at least one Pro Basic or Pro Business seat on the Billing page, then try again. Viewer seats alone are not enough.
Captcha verification failed. Please try again.	Complete the verification box again and resend.
This migration link is invalid or has expired.	The user's link is older than 7 days. Send a new request.

Audit log

Both halves of the move are recorded in your team's Audit Log. You will see an entry when the request is sent, and another when the user approves and the maps move.