Violation of PRIMARY KEY constraint in SSMS import/export wizard
Start by narrowing it down. Does it happen with only this one table? What if you play around with the scripting options (still only doing this one table); uncheck &quot;everything&quot;. Etc. Until you have something working and then add bits and pieces back on until you find which one breaks it.
In the end, this is either a problem in the wizard (since duplicates cannot occur in the source data when you have a unique index), or we don't have the full story (hence my recommendation to narrow it down).
If it is a problem in the wizard, then consider reporting it to MS. They will likely want a repro for your problem.