Hi. It sounds like you're talking about importing with a different package
into this. Just for your background, while this package puts users into
groups, there is a lot of other stuff happening in the background to try to
manage the ways that dates need to be tracked.

So, no, currently out of the box there are is no way to not only put them
into a group, but put them into a membership.

But I'm open to adding this soon for you, depending on what the final
requirements are. (Basically, if we can do this in a relatively simple way
without making it "fully featured".)

Once again, for context, this addon tracks things mostly as "products"
rather than "groups". That's what things like renewal emails will be based
on.

So, it sounds like you don't just want to import groups, but "products".

* How many for a given user? Is 1 product fine, or do you want multiple?
* What are your expectations about how the "transactions log" will look? Is
it fine if they appear as a transaction where you were credited with money
on the date that you specify?
* Anything else?

James

The way I've set it up is that each Membership product is named to a corresponding User Group, i.e. Basic Membership places members into the Basic Membership group. There is an option to have that membership expire. I assume a date is stored with a user's information to determine what a year, month, etc. would be. I have that field populated in my csv file.

I intended to use your user import package to import all of these users and can place them into the correct group (according to the description of the package). I assume the date the user was placed into the group is part of the Subscription package and not part of the core C5 users information, but they have to communicate with each other somehow already, correct?

Unrelated: These users will need to be notified that their membership will be expiring and need to renew.

I hope that all makes sense!

Yes, it stores the expiration date, but it stores a lot more than that.
While you could probably create the "membership" record after the fact (ie,
after they're already in the group), that won't work out of the box. The
most obvious problem to me is that the addon will see that they're already
in "Basic Membership" and say "this person is already in the group. why
should purchasing a product keep them in that same group but remove them
later". Basically, a check to make sure the user isn't already a "lifetime"
basic member. And I'm sure there's similar stuff.

So if you want the appropriate membership record, you really should do it
the right way, which is to create it using the code, which will put them
into the group, set up the record for expiration / notifications / etc.

It's good to know that you only need to specify one product at a time. That
makes the potential CSV easier. I'm thinking something like "membership"
column with a value like "Basic Membership|12/31/2013".

However, I'm still wondering if you have any expectations to how the
transaction will be recorded. See my previous post for explanation on this.

I think the transaction log should contain the date the transaction happened and what type of membership (product) the user chose.

I think the 'membership' column for the csv will work since I already have that column in the csv file I will be importing. A lot of the other columns in the csv file may not relate to the subscription package, but the C5 core user attributes.

Would it be possible to move a user to a different group after a specified amount of time, i.e. if their membership hasn't renewed by the 1-year or 1-month period, they move to a group that doesn't get displayed on the site?

Most of this is me thinking out loud.

Any updates on this?

Hey there,

I need the same solution. Need to import users from a already existing membership page, payment information seems not to be needed, just the expiry date to make expiration and notification work.

It is all about one group, one product - just many users.

How would I go about doing this?

(Using both the Lertecos)

Thank you!

Hi.

I did this back in November and it's part of the current source. I did some testing this morning and found a few issues and released a new version (2.0.2), so make sure you upgrade to that. With that being said, I don't think Tony or anybody else ever tested it in the wild, so you might want to make a back up in case there are any issues... but it looks good here.

If you have membership package installed you should get a new importable field to drag-and-drop to (under username, password, etc). Just make sure your memberships column is dragged over there.

The format is like groups, with product names separated by |s. Some of the complication is setting the import date (you can't set the expiration date, so you'll have to do math based on your product duration), which you separate from the product name with a semicolon. If you've only got one product named "My Product", the column value will be simply:

My Product
or
My Product;1 Feb 2013

(That will create the product as of 1 year ago. Assuming My Product has a 1 year duration, it'll expire on 1 Feb 2014.)

James