Well, there's always Multimaps.newXXXMultimap, though that requires that the map be empty; there's also Multimaps.forMap, which views a Map<K, V> as a Multimap<K, V>
But what you're probably asking is about Map<K, Collection<V>>.
IIRC, the reason we haven't necessarily decided to accept those issues yet is that we're having trouble coming up with use cases where the "Right Thing to Do" is to convert a Map<K, Collection<V>> to a Multimap<K, V>, instead of using a Multimap from the beginning and never bothering with a Map<K, Collection<V>> at all.
Of course, there's also the perfectly good workaround of
for (Map.Entry<K, Collection<V>> entry : map.entrySet()) {
multimap.putAll(entry.getKey(), entry.getValue());
}