Sure! There are a few different ways I can think of.

1. manually create users
2. manually create using Selenium to physically create a user entry (hacky but hey - I'm brainstorming here!)
3. Using custom logic - so if you are on the latest versions of Umbraco 7 you could use the Umbraco UserService

4. Custom SQL logic to create the users in the relevant tables in the database ([dbo].[umbracoUser] or [dbo].[cmsMember*] prefixed tables for Member import)

   UmbracoContext.Current.Application.Services.UserService.CreateWithIdentity("username", "[email protected]", "mybadpassword123", "myUserType");

See this post for a similar question. Really all depends on your data source and how many you are importing. Don't forget that Umbraco uses the standard ASP.NET membership provider. There are 2 - one for Members and one for Users. They are both specified in the web.config. This means you can write your own custom provider to replace Umbraco's. A common example of this would be where you wanted to use say ActiveDirectory as the login provider.

<membership defaultProvider="UmbracoMembershipProvider" userIsOnlineTimeWindow="15">
  <providers>
    <clear />
    <add name="UmbracoMembershipProvider" type="Umbraco.Web.Security.Providers.MembersMembershipProvider, Umbraco" minRequiredNonalphanumericCharacters="0" minRequiredPasswordLength="4" useLegacyEncoding="false" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="false" defaultMemberTypeAlias="Member" passwordFormat="Hashed" />
    <add name="UsersMembershipProvider" type="Umbraco.Web.Security.Providers.UsersMembershipProvider, Umbraco" minRequiredNonalphanumericCharacters="0" minRequiredPasswordLength="4" useLegacyEncoding="false" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="false" passwordFormat="Hashed" />
  </providers>
</membership>

Rockstar on the 3rd one. Worked easily.

Is it possible to give them access to sections and set a login name separately? The process still requires manual cleanup otherwise.

-Amir

The way to do it is to use different usertypes for your access configuration and then just create the with that usertype. What do you mean by cleanup?

is working on a reply...