azure-migrate | Applications | Import applications

Question

azure-migrate | Applications |

When I go to Import applications > select the "Export all inventory" link and export > and then edit the respective row in the csv > I am unable to import the same edited csv > suddenly the "id" column name is now incompatible??
(and obviously, I have not edited the column headers).
I have only updated the Application Names(s) eg App-1, App-2 per row. Nothing else.

Any advise?

Answer 1

Thanks for posting your question in the Microsoft Q&A forum.

The import fails because editing the CSV, often adds hidden formatting or encoding changes so even if you didn’t touch the id column, its format may have been altered. Things like BOM characters, encoding changes, extra spaces, or blank lines can break Azure Migrate’s parser.

The fix is to edit the file in a plain text editor, keep the id column exactly as exported, save as UTF-8 with no extra characters, and make sure there are no hidden spaces or empty rows. Once the CSV is clean, the import should work.

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful

Answer 2

Hello Allen Visser (EMEA), 

Thank you for posting your query on Microsoft Q&A portal.

Here are a few things to consider:

1. Column Names: Even though you mentioned that you didn't edit the column headers, please double-check to ensure that they match exactly with what Azure Migrate expects. It's crucial that the case and spacing are identical.
2. CSV Format: Sometimes, when editing CSV files, the formatting can change slightly (like additional spaces or commas). Make sure there are no extra commas after the last field in the rows or trailing spaces in the ID column.
3. ID Column Incompatibility: If you're getting an "incompatible" error related to the "id" column, this may indicate that the values in that column are not aligning with those in the system. Review the values you have in that column to ensure they are valid and correspond to the applications you are working with.
4. Supported Import Actions: Remember that the import currently only supports adding application names linked to workloads. Other details like properties or tags might not be supported.

If you've checked these points and are still having trouble, it might be helpful to gather some additional details. Here are some follow-up questions:

1. Which specific error message are you seeing during the import process?
2. Could you share a sample of the CSV structure you are using?
3. Have you checked the Azure Migrate job logs for any additional context on the error?
4. Are there any specific metadata attributes in the ID column that you think may be relevant?

I hope this helps to get you on the right track! If you need further assistance, feel free to ask!

Reference List

• Migrating web apps to Azure App Service
• Azure Migrate App Service Migration
• Azure Migrate - Define applications
• Common issues with Azure Migrate