Hi Gregory,

There are a lot of different ways to pull this off, but you can always have a workflow that runs on the current item based on whatever condition you need that uses the "Update Item" action to update the column you created with the ID property.

For example, on List A you could have a workflow that runs on Item Create that simply sets the item's own column (let's call it TrackingNumber) to be equal to the value of its own item ID.   So when you move the data from one list to another, you'll have the "old id" stored in its TrackingNumber column.    To give you a more exact solution I'd have to hear more about what you are working with, but this should get you going down the right path.

Thanks,
Mike

Thank you for the quick response. I get an error when attempting this.

The new field (TrackingNumber) is a number field in order to use in a calculated column later. When I try to configure the 'Update Item' action, it says that I need to enter a numeric value to save - it will not let me enter 'ID'. (as seen in the picture attached above)

"Value" in the dropdown box means the literal value that you type in that text box, so it's literally trying to put the string "ID" into a number field.

You need to select List Lookup from that dropdown box, then in the Source dropdown select Current Item and then in the Field dropdown select ID.

You can also make New ID a text/string type and then it should accept your value.  Depends if you care/need about keeping it as a number type.