In order to import your existing account and member data or wait list data into Member Splash it needs to be organized in one of the specific file formats listed below:
- Csv - Comma Separated Values
- Xlsx - Microsoft Excel
To ensure that the migration is as smooth and accurate as possible, we encourage you to, first, review the documents below to assist you in the process of formatting and sending us your data file:
Single Rows of Data Per Account
Each of your member accounts consists of two types of data: account data (like the street address and account type) and member data -- the information for each person on the account. To import your data into Member Splash each account and associated member records should be on a single row in your data file.
Example of Data on a Single Row
|Account Type||Address||City ...||m1first||m1last||m1type||m2first|
|Bondholder||123 Any St||Washington||Rob||Smith||Adult||Susie|
|Seasonal||555 Willow St||Bethesda||Rachel||Jones||Adult||Tom|
Standard (and Required) Account Fields
Member Splash has a default set of account fields that are common to all clubs. Each of these fields would be a column in your data file with the field name in the header row. All fields are optional except username, acct_type, payment_status, m1first, m1last, m1type those marked with a red asterisk (*).
Custom Account Fields and Notes
In addition to the standard account fields Member Splash supports unlimited custom account fields as well as account notes.
Custom Account Fields are used to track a single value. For example, many clubs require the purchase of a bond upon joining that is refundable if the account is closed. Those clubs may want to track the bond amount paid in a custom field. To do so simply add it as a column after the standard account fields as shown below. Custom fields are stored as strings in the database which means that they can include text, numbers and special characters like currency signs.
Example showing two Account Custom Fields
|Zip||...||Bond Amt Paid||Date Bond Paid|
Account Notes are a flexible catch-all type of field that can be used to store more complicated or non-standard information. For example, tracking an issue with a specific account. Accounts can have unlimited account notes and account notes can be categorized. To import account notes add them as columns after the standard and custom account fields, as shown below.
Example showing Account Note Fields
|Account Note 1||Account Note 1 Category (optional)|
|John Smith contacted the club on 10/1/2013 stating that they had not received their renewal notice in the mail and consequently felt they should not be charged a late payment fee. Club agreed to issue a credit for $50.||Payment Issue|
Each member record in Member Splash has a standard set of fields, listed below. Those that are required are marked with a red asterisk (*). There are two important requirements to note when organizing your data file:
- The first member listed in each row is marked as the billing contact. This is the person considered to be the primary contact for the account. Your terminology may vary (shareholder, voting member, etc.), the key is that they must be the first person listed.
- Each member field should be prefixed with the letter m and a number. This is what allows Member Splash to correctly link the data for each individual member. Suppose an account has three members, two adults and one child.
Example showing Member Fields
In the example above Bob Smith will be marked as the billing contact for the account.
The available member fields are:
Data Formatting and Consistency
The biggest challenges with importing data accurately are inconsistent formatting and incorrectly stored data.
Problems with formatting data? Read: Data Formatting Tips
Example of Inconsistent Formatting
Many data formatting issues can be corrected easily in Excel. In the example above using Excel's Cell Formatting options would allow you to specify that the column should be in the format yyyy-mm-dd. Data that is stored incorrectly, however, may require manual cleanup.
Example of Incorrect Data Storage
In the example above there are multiple email addresses as well as descriptors in the m1email field. Because the importer expects a single email address that record will get rejected.
What to do if your data is a disaster
First, take a deep breath! Most swim clubs have been run more or less by hand for decades. When you're tracking things manually there is nothing to enforce consistency and with different volunteers and policies over the years it's inevitable that the information will get messy.
The team here at Member Splash is adept at advanced scripting to automate cleanup and if you're stumped on how to handle some of your data we're happy to provide data cleanup and formatting services for an additional fee of $100/hour. If interested, please contact our Support Center.
But if it's really a mess? Dump it. Literally. Aside from any issues with how the data is stored or formatted, many clubs have lots of incomplete or out-of-date information. Rather than starting off with bad information we recommend that in those cases we simply import the minimum data necessary to create the accounts -- street address and billing contact name -- and you have the members enter their current information the first time they log into the system.
Was this article helpful?
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
We appreciate your effort and will try to fix the article