How does EV know not to target aready-archived items

Hi Guys,

We are migrating from an older EV environment to a newer one using a third-party migration tool which will change the shortcuts as it moves the archived items. The following question came up:

- How does EV know that an item is already archived so it does not try to re-archive a shortcut in the new EV environment?

a) Does the archiving task do a scan every time and check message classes hence bypassing EV shortcut message classes?

b) Or does it keep  tab somewhere in an sql table for items already archived?

Thanks,