If a CSV row carried an invalid value in a URL-type custom field — say a
Website cell holding http://www.example.com; www.example2.com, or an address
missing its http:// — the whole row failed with “Value must be a valid URL”
and the contact was never created. A valid name, email, phone, company and
address were all thrown away because of one optional field.
Date custom fields already degraded gracefully on import: an unreadable value
is skipped, the contact is still created, and the completion screen shows a
warning naming the cell. URL fields (and any other custom field whose value is
rejected) now behave the same way.
What you may notice
Rows that previously showed up under “failed” with a URL error now import
normally. The completion screen lists a warning for each skipped value —
naming the field and the exact cell contents — so you can fix the value on the
contact afterwards.
What this doesn’t change
The invalid value itself is not stored or auto-corrected. A cell with two
URLs, or one without a protocol, is left blank on the imported contact and
reported for manual cleanup.