Right, this may seem like an odd question. I have 2 amember databases from 2 different sites. One has around 20,000 members while the other has about 5,000. I wish to make these 2 databases into 1 database to use on 1 site. However, because the databases are a reasonable size, there will be some of the same usernames in each database. Now ideally what I'd like is every member that is active to stay active, regardless of whether they are active on 1 or both of the databases. How would I go about this? All suggestions welcome, Cheers
First export both databases into .csv files and do a quick check to see how may duplicates you are talking about (import into excel. get the count. push the "Remove Duplicates" button. compare the count).. if you are dealing with < 100 it is probably not worth sweating the details (especially if you check the activity level of those < 100.. If it is a large amount, perhaps convert the dupes to make their email addy as their username and send them a message indicating such.
Thanks skippy but I have another problem: User ID #s Both databases will have user 1,2,3 all the way up to 5000. Is the amember_payments table not based on User Numbers rather than usernames? Thanks for your help so far as I've managed to get them both up in excel. If you can get your head around this one I'll be forever greatful.
First off, were you able to figure out how many duplicate usernames you have between the two databases? As far as payments, unfortunately aMember does not provide a mechanism for importing payment records so it will be a manual process of some kind anyway.. 1) How many different product types do you have? 2) Do you have one time payments or reoccurring payments?
There are around 300 duplicate usernames. 1) Well, say around 400 product types Not all active of course. 2) Around 40-50 of 1200 active members are recurring PayPal payments
Ugh.. I was hoping you had a small amount of product types and no recurring.. Unless someone else has done this before, at this point I think your best bet is a support ticket into aMember as there are a number of complexities into making this work. I wish I had a better answer for you.