Power Automate

data migration issues

(0) Share

Report

Posted on by RN-07051437-0

Hi Everyone,

I am facing an issue while migrating data from Excel to SharePoint using Power Automate.

Scenario:

I have an Excel sheet containing data.
Using Power Automate, I mapped all Excel columns to SharePoint columns.
The flow runs successfully without any errors.
In the Dev environment, all fields are populated correctly.
After moving the solution/flow from Dev to Production, one specific field is not getting populated in SharePoint, while all other fields are working fine.

Things I checked:

Field mapping looks correct
Flow status shows Success
Excel contains values for that field
Other fields are migrating properly

My question:

Is this a common issue during Dev to Prod migration?
Could this be related to SharePoint internal column names, column type mismatch, or connection references?
Has anyone faced a similar issue where only one field fails in Production?

Any suggestions on what exactly I should verify would be helpful.

Thanks!

Categories:

Power Automate Mobile App

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Vish WR 3,748 on at

Like
a
(0)

Report
Copy link

Link copied!
@RN-07051437-0

This usually happens because something is different between Dev and Production for that specific SharePoint column, even though the flow migrated successfully.

Most common things to verify:

Check the SharePoint internal column name in Prod. Sometimes the display name is the same, but the internal name is different after migration or column recreation.

Verify the column type matches exactly in both environments (Single line, Choice, Lookup, Person, Number, Date, etc.).

Recheck connection references and permissions in Production.

f it’s a Choice, Lookup, or Person column, confirm the values exist and are valid in Prod as well.

Open the Flow run history and inspect the “Create item/Update item” action output to see whether the field is being passed as blank or rejected silently.

Also confirm the column is not marked as read-only, calculated, or requiring special formatting/validation in Production.(different from DEV)

Vishnu WR

LinkedIn - My Tech Space

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥

Was this reply helpful? Yes No
David_MA 14,956 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

For the production flow, does it point to the same SharePoint site/list as the development one? If not, have you checked to make sure that the field settings on the field that is not syncing correctly configured exactly the same?

Was this reply helpful? Yes No