Additional extended information can also be included; even Custom Fields:
"ID","Username","Password","First Name","Last Name","Display Name","Email","Website","Level[0-9]+ or Role ID","Custom Capabilities","Registration Date ( mm/dd/yyyy )","First Payment Date ( mm/dd/yyyy )","Last Payment Date ( mm/dd/yyyy )","Auto-EOT Date ( mm/dd/yyyy )","Custom Value ( starts w/domain )","Paid Subscr. ID","Paid Subscr. Gateway","Custom Field ID #1","Custom Field Value #1","Custom Field ID #2","Custom Field Value #2", ...
Here is a full example with all fields filled in, including extended details; and two Custom Fields:
"","johnsmith22","mY!passwrD","John","Smith","John Smith","john.smith@example.com","http://www.example.com/","2","music,videos","12/31/2000","01/10/2001","12/31/2020","12/31/2021","www.example.com|123.357.125.654","I-2342934SSER243","paypal","interests","fishing,biking,computers","t_shirt_size","xx-large"
Statistics: Posted by Cristián Lávaque — August 18th, 2011, 2:41 pm
If you supply Custom Fields, your Custom Field IDs need to match up with the Custom Field IDs you've configured with s2Member. See: s2Member -> General Options -> Custom Fields. If you have a Custom Field that contains an array of multiple values, you can import the array using PHP's serialize() function. This allows you to convert the array into a string representation. s2Member will automatically unserialize the value during importation. If you have any trouble, please perform an export first. s2Member's export files are already formatted for easy re-importation. In other words, you can use them as a guideline for building your own import files.
Statistics: Posted by craigjb12 — August 18th, 2011, 7:50 am
Statistics: Posted by Cristián Lávaque — August 18th, 2011, 2:00 am
Statistics: Posted by craigjb12 — August 17th, 2011, 3:03 pm
Statistics: Posted by craigjb12 — August 17th, 2011, 2:43 pm