Strange Behavior from Data Export - Changes Table Definition

Hello. I was wondering if anyone has experienced strange behavior when performing a data export.

The source table, which is defined with a primary key and which has data is recreated in the destination database, on the same SQL Server, without a key and having at least one column definition changed from nullable to not null.  The source table also appears to have the same field as not null.

However, a script I produced prior to doing the export, has both the primary key and proper column definition.  

It seems the behavior changes when there is data versus no data.  

Edit: I'm working with SSMS 13.0.16106.4 and SQL Server 2016 13.0.6300.2

- Nick