If you all the columns are site columns with exactly the same names and there should be no issue. Sometimes you can only see the original column name in the url when you're editing it. Calculated columns are linked ot other columns - if the looked up column on the new list is not exactly the same (check the URL, whilst editing), there may be issues. Using the same site / content type columns should prevent this.

Hi Pierre,

Shaunlub is correct in saying that if all column names referenced in the import exist they will be mapped correctly, this enables moving workflows across sites. However the expected behaviour on importing a workflow to a site where a list/column does not exist is simply to invalidate the token, so the action will be unconfigured when imported because there is no match. The corrupted error message is not expected at this point.

Are you getting a correlation ID with the error message on import? It may be worth contacting Nintex support on this as it is not the expected outcome when there is something wrong with a field.

Thanks

Callum

Hello again,

Thank you for your answers.

The problem is not about the internal name of the columns. It's a list workflow, I tried to import it on the same list and I still have this error.

I have a correlation ID, and I'm talking with the support right now.

I'll let you know what it's all about.

Regards,

Pierre Nouet