Lead-to-account matching can only be triggered off a Lead. Contacts-only orgs (no Lead object) have no way to match an existing Contact to the correct Account, so a contact parked on an orphan/placeholder account can't be reassigned to its real account without external tooling.

Let Contact be a valid trigger object for the account-matching algorithm, so admins can match an existing contact to an account (and update the account relationship) using the same matching logic available for leads today, without creating or converting a lead.

Contacts-only CRMs are a growing segment. Forcing a lead as the matching input excludes them entirely and pushes them to competitors (e.g. LeanData's direct contact-to-account node) or to maintaining a separate in-CRM agent. This blocks a 40-day LeanData replacement and has come up as a "we've never run into contacts-only before" surprise internally.