Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Migration : User mapping

Bunmi Alaka
March 10, 2026

The Problem: Identity String Mismatch

The native Confluence Importer for Notion relies on a strict 1:1 email string match to attribute page history, "Created By" metadata, and in-line @mentions.

Because the source identities exist as user@unleash.so and the destination identities exist as user@zendesk.com, the importer will fail to recognize the users. Without manual intervention or source-data alignment, the importer will default all migrated content—thousands of pages and edits—to the Admin account performing the import, permanently erasing the historical context of who authored the documentation.

1 answer

0 votes
Benjamin
Community Champion
March 10, 2026

HI @Bunmi Alaka ,

 

The accounts usually would need to match up prior to migration. That's the key is uses to map all the objects. Either the source needs to be updated or the destination. Source would be preferred. Ones the importer is done, all the data is mapped to the intended user.

 

-Ben

Bunmi Alaka
March 10, 2026

We are not able to change the address from source. That is the challenge we are facing. 

 

Benjamin
Community Champion
March 10, 2026

Hi @Bunmi Alaka ,

 

Then the other option is to match up on the destination side. I would recommend reaching out to atlassian support through their service desk and raise a ticket. Perhaps, there might be something that can be done on the back end or possibly an alternative solution. 

 

-Ben

Bunmi Alaka
March 10, 2026

Thank you!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events