That's interesting, I've run into a very similar situation recently. One possible idea might be to associate both "M. Smith" records to a single custom object that represents the actual person of M. Smith (as opposed to the CRM contact). Then, rather than sync the contact record, one would sync the custom object record instead. This means that whether it's M.Smith #1 or M. Smith #2 that is currently active, they both tie back to the same CO, and that is the record that gets synced.
Of course, there are pros and cons to this idea, but it is one way to do it, as I understand your scenario. Thoughts?
That would not fly because there are far too many limitations on what you can (or rather cannot) do in Marketo with custom objects:
- Impossible to use the data to personalize emails except through Velocity, which is a language that most Marketers can use
- No triggers on field value updates
- No possibility to use custom object fields in forms