Just thought I would share this little tip to prevent someone else having the same issue:
The Configuration Data Migration Tool is a great way of moving records such as custom auto number settings from one organization to another. You can find it in the SDK under SDK\Tools\ConfigurationMigration.
When configuring the data schema, you are prompted to select the entities and the attributes that you would like to export and then eventually import. This seems like this is all that is required before hitting 'Save and Export' – but be warned there is one more important step if your data does not have unique display name values.
In my example I had two records that had the same name and they already existed in the target organization. Normally, the tool will use the display name attribute to perform a lookup rather than use the primary unique identifier for the record. The result will be that the same record will be updated twice in the target, rather than the two separate records being updated accordingly.
To ensure that the primary name field is not used as the lookup on the target system you must select 'Tools->Configure Import Settings'. This then gives you the option to select the primary key field that you want to use other than the display name:
You can no click 'Save' and export your data knowing that the primary unique identifier field will be used to match the records between the source and destination.
The xml schema file created adds the magic 'updateCompare' attribute to the xml and you are good to go!
<field updateCompare="true" displayname="Counter" name="xbitz_counterid" type="guid" primaryKey="true" />
You can learn more about this very useful tool here - https://technet.microsoft.com/en-us/library/dn647422.aspx Hope this helps!
@ScottDurow