Below is an explanation of the column headings and what they mean. Your file must include a user_email column. Every other column is optional, including the membership columns, so you can import or update users without changing their membership.

WordPress User Columns

  • user_login: The unique username for this user.
  • user_email: The unique email address for this user. This column is required.
  • user_pass: The password to set for this user. We do not recommend importing passwords. Leave blank to generate a random password for new users.
  • first_name: The user’s first name.
  • last_name: The user’s last name.
  • display_name: The desired name that displays for this user when reference on the frontend or backend of the membership site.
  • role: The desired user role for this user. Leave blank to set to site default for newly imported users. Existing users keep their current roles when this is blank. To give a user more than one role, separate the roles with commas, such as subscriber,contributor. We highly recommend keeping the role set to “subscriber”.
  • user_url: The user’s website.
  • description: The user’s biographical info.
  • nickname: The user’s nickname.
  • user_nicename: The URL-friendly version of the user’s name, used in author archive links.
  • user_registered: The date the user registered, in UTC (formatted as YYYY-MM-DD HH:MM:SS). Leave blank to use the time of import for new users.
  • ID: The WordPress user ID of an existing user to update. A row with an ID always updates that user, even if Update Existing Users is unchecked. If no user has that ID, the row is not imported.

Other columns can be saved as user meta. On the mapping screen, map them to a User Field or to “Custom User Meta”. Columns left as “Skip” are not imported. See Import User Custom Fields below.

Updating Existing Users

The import matches each row to an existing user in this order:

  1. By the ID column, if your file has one. This always updates the matching user.
  2. By user_login, then by user_email, but only when Update Existing Users is checked on the import screen.

Rows that don’t match an existing user create a new user. If Update Existing Users is unchecked and the username or email address is already in use, the row is skipped and listed in the error log.

When you update a user, blank cells are skipped. They don’t erase the data already saved for that user. To clear a user’s first name, last name, website, or biographical info, enter 0 in that column.

PMPro Membership Level Columns

The only field required to give a user a membership level is membership_id, but it’s best to fill out as many fields as possible. By adding more fields, you also import the correct “subscription price” (shown on the Membership Account page) for imported members. If your file doesn’t include membership_id, or a row’s membership_id is blank, that user’s membership is not changed.

  • membership_id*: Membership numerical level ID of the user’s membership level (not the level name). Navigate to Memberships > Settings > Levels to obtain your site’s level IDs. Note: Importing the value “0” will cancel all of the user’s existing memberships.
  • membership_initial_payment: The initial payment for the user’s membership level (the amount collected at checkout).
  • membership_billing_amount: Specifies the billing amount for the user’s membership level, such as ‘250’ for a level billed at $250 per year.
  • membership_cycle_number: Specifies the billing cycle number of the membership level, such as ‘1’ for a level billed once per month.
  • membership_cycle_period: The billing cycle period. Possible values are “Day”, “Week”, “Month”, and “Year” (without the quotes).
  • membership_billing_limit: The billing cycle limit for the user’s membership level.
  • membership_trial_amount: The trial amount for the user’s membership level.
  • membership_trial_limit: The number of cycles the trial should last for the user’s membership level.
  • membership_status: The status of the user’s membership. Possible values: active, inactive. An inactive membership is given to the user and then cancelled through PMPro’s standard cancellation, so integrations such as LearnDash remove the access they granted. The member shows as an old member, and their gateway subscription is not cancelled.
  • membership_startdate: The member’s start date. (formatted as YYYY-MM-DD)
  • membership_enddate: The date membership expires and is fully cancelled. (formatted as YYYY-MM-DD). You should only import an end date for members that should fully expire and cancel. Do not set an end date for a member with a lifetime membership or an active recurring subscription. If you don’t include a time, the member keeps access through the end of that day. An end date in the past is handled the same way as an inactive status.
  • membership_timestamp: Date to use for the timestamp of the order we generate on import. Generally the last payment date for the member. (formatted as YYYY-MM-DD). We only create an order when the row includes both membership_subscription_transaction_id and membership_gateway, or a discount code.
  • membership_code_id: Discount Code ID (if used) found on the Memberships > Settings > Discount Codes screen in the WordPress admin.
  • membership_discount_code: Value of the discount code (if used) found on the Memberships > Settings > Discount Codes screen in the WordPress admin.

*required to assign membership levels

Importing Multiple Memberships Per User

If you have multiple membership levels to import for the same user, you can use this import tool by following these steps:

  • Create duplicate rows in your CSV for each membership level you need to import for the same user, and check Update Existing Users when you import. Otherwise, the second row for a user is skipped because the username and email address are already in use.
  • You can only import additional membership levels for level groups that allow multiple levels within the group (you cannot import two memberships for levels in a “one per” level group).
  • Additional rows of data for the same user will overwrite their WordPress user fields, including custom user meta fields and billing fields. Blank cells are skipped.

We recommend first importing all the users without any membership details, then run a second import for the membership information with Update Existing Users checked. In this second import, remove all unnecessary user information (password, role, name, custom user fields). You only need the user_email field to match the existing user (from the first import) to the membership data import.

Maintaining Active Subscriptions

For sites that want to continue or update an existing subscription, your import file must contain the membership_subscription_transaction_id and membership_gateway fields.

Without these fields, PMPro’s gateway integrations will not know which user to attach a new incoming gateway message to (new order, failed payment, subscription cancellation).

PMPro Subscription Columns

  • membership_subscription_transaction_id**: The gateway’s Subscription Transaction ID (required) if you want to continue or update an existing subscription. You can find this data on the Memberships > Orders page in the WordPress admin.
  • membership_gateway**: The Payment Gateway for the user’s recurring subscription. Possible values are “check”, “stripe”, “paypalstandard”, “paypalexpress”, “paypal”(for website payments pro), “payflowpro”, “authorizenet”, and “braintree” (without the quotes).
  • membership_payment_transaction_id: The gateway’s Payment Transaction ID (optional). You can find this data on the Memberships > Orders page in the WordPress admin. This field is useful as a reference for a user’s last payment made between the site and your gateway. For import, you set this to the last single transaction ID received as part of the users’s subscription.
  • pmpro_stripe_customerid: If you are using the Stripe gateway, include this column in your import. On the mapping screen, set this column to “Custom User Meta” so it’s saved with the pmpro_stripe_customerid meta key.
  • membership_order_status: The status of the order we create on import. Defaults to “success”.
  • membership_affiliate_id: An affiliate ID to save on the order we create on import.

**required to update recurring subscription

Import User Custom Fields

  • You can import any custom field that you have added to your WordPress site using Paid Memberships Pro User Fields.
  • You can also import custom fields for other uses on your site, such as customer data for WooCommerce.

To import custom fields, add additional columns to your import file where the column name is the unique meta_key used for your user field. Then check how each column is mapped on the Map CSV Fields screen.

PMPro User Fields

Your User Fields appear in the Maps To dropdown, grouped by field group as “[Group Name] (User Fields)”. Each field is listed by its label followed by its name, such as “Company (company)”. When a column heading matches a User Field’s name, that field is selected for you.

Maps To dropdown on the Map CSV Fields screen showing a User Fields group and a field selected automatically from the column heading
  • Fields with multiple values: For checkbox groups, multi-selects, and other fields that save more than one value, separate the values with commas. You can use either the option keys or the option labels.
  • Date fields: Dates are saved in YYYY-MM-DD format. Common formats such as 03/15/2026 are converted for you. Values we can’t read as a date are saved as entered.

Other User Meta

For a column that isn’t a User Field, choose “Custom User Meta” in the Maps To dropdown. The meta key is the column heading in lowercase, with spaces and special characters other than dashes and underscores removed. For example, a “Company Name” column is saved as companyname. The mapping screen shows the meta key before you import.

Other Add Ons can add their own import columns to the mapping screen. For example, the Lock Membership Level Add On adds a “Lock Membership Level” group so you can lock members as you import them. See Import and Export Locked Members for the columns and values.

Parent/Child Relationship Import

To import members that require a parent/child relationship, configure the PMPro Group Accounts Add On and follow the import steps.

Last updated on November 12, 2026


Was this article helpful?
YesNo