Short Answer: Yes.  Longer Answer:  Obviously, this will happen at cut-over time unless you're using something like DFS to handle the namespace.  There are two ways I'd look at doing this:  1. If you can truly merge the servers (i.e. the share names don't clash, you're all under the same authentication providers, etc). you could set up the shares and use SmartConnect Zone aliases to allow the names to resolve to the same IP pool.  2. If you can't merge the servers, you can set up the servers in separate access zones each with its own SmartConnect zone with its own name that matches the name of the previous server.  in this case, you can have share name clashes and, if needed, different authentication providers.
At this point, this is almost a Yes/No question from me but any elaboration is appreciated.  I've had about a day's worth of poking around on a brand new isilon system and have read how different network configurations and access zones can be setup.  We'll be migrating data from about 10 different Windows file servers and NetApp CIFS SVMs to a 3-node Isilion system running OneFS 8.  Keeping  \\fileservername\sharename without using \\fileservername.isilon\sharename would of course be incredibly convenient.  I do have an appointment with professional services this week but getting a basic answer would be helpful.  TIA
Possible to migrate to Isilon and keep file server names?