Any Guid will do since it doesn't relate to the rest of the fields so just use NEWID() in your select statement when you insert the customer records:
INSERT INTO Customer
(CustomerGuid
,Username
,Email
,[Password]
,PasswordFormatId
,PasswordSalt
--,AdminComment
,IsTaxExempt
,AffiliateId
,VendorId
,HasShoppingCartItems
,Active
,Deleted
,IsSystemAccount
--,SystemName
--,LastIpAddress
,CreatedOnUtc
--,LastLoginDateUtc
,LastActivityDateUtc
--,BillingAddress_Id
--,ShippingAddress_Id
)
SELECT NEWID()
,CUSTNMBR
,Email
,HashedPassword
,1 --PasswordFormatId
,Base64Salt --PasswordSalt
--, AdminComment
,0 --<IsTaxExempt, bit,>
,0 --<AffiliateId, int,>
,0 --<VendorId, int,>
,0 --<HasShoppingCartItems, bit,>
,1 --<Active, bit,>
,0 --<Deleted, bit,>
,0 --<IsSystemAccount, bit,>
--,<SystemName, nvarchar(max),>
--,<LastIpAddress, nvarchar(max),>
,GETUTCDATE() --<CreatedOnUtc, datetime,>
--,<LastLoginDateUtc, datetime,>
,GETUTCDATE() --<LastActivityDateUtc, datetime,>
--,<BillingAddress_Id, int,>
--,<ShippingAddress_Id, int,>
FROM PasswordUsers
I've also got a complete version of a customer import stored procedure which includes generating random salts and using them to correctly hash and encode existing user passwords if it would be useful?