There is no easy solution FOR this, I'm affraid. The two solutions I can think of are:
1) SSIS package: create OLE DB source and destination, and make it ignore truncation errors.
2) A stored procedure to Alter each nvarchar(255) columns to its corresponding column length on the destination table (taken from information_schema.columns)
In both cases, the fact that the column names match, makes the task not too daunting.