Eleo 2.0 Pre-Conversion Checklist
Eleo 2.0 is coming! To ensure your move is seamless, we’ve created a checklist of important action items for you to complete PRIOR to your migration. Following these steps will help ensure the data you need is transferred or saved accurately. If you need assistance, the Support Team and Tech & Admin Staff are here to help!
Keep in mind, your Eleo 1.0 database will remain accessible in ‘View Only’ mode after the migration, allowing you to review any items or data that were not transferred.
Custom Fields
What you need to know: To improve the speed of Eleo, the number of custom fields in Eleo 2.0 has been limited to 20 fields within the Contacts and 20 fields within the Gift Module: 10 text fields, 5 numeric fields, and 5 date fields per module (click here to learn more). Any custom fields outside the Contacts and Gifts modules will not transfer to Eleo 2.0.
To Do:
☐ Review the custom fields in your Contacts module, and determine up to 20 custom fields you want to be transferred (remember, you can have 10 text fields, 5 number fields, and 5 date fields).
☐ Review the custom fields in your Gifts module, and determine up to 20 custom fields you want to be transferred (remember, you can have 10 text fields, 5 number fields, and 5 date fields).
☐ Delete any custom fields you no longer need.
☐ Delete duplicate custom fields.
☐ Download and save any Custom Fields that are outside the Contacts and Gifts modules to your computer (remember, these will not be transferring).
Volunteer Module
What you need to know: The Eleo 2.0 Volunteer Module has been simplified.
The following fields have been eliminated:
- Attended Training
- Volunteer Training Date
- Attended Orientation
- Volunteer Orientation Date
- Background Check
- Volunteer Background Check Date
- Volunteer Skills
- Volunteer Days
- Volunteer Times
The following fields will remain:
- Volunteer Interests
- Volunteer Status
To Do:
☐ Download and save the volunteer information you wish to retain using the Contact Report Writer.
Contact Lists
What you need to know: Only static lists will transfer to Eleo 2.0, dynamic lists will NOT be carried over (but most can be re-created).
To Do:
☐ Delete lists you no longer need.
☐ Identify the dynamic lists you’ll need after the move. Record each list’s name, along with all filters and criteria applied, so you can easily recreate it in Eleo 2.0.
Pro-Tip: Your Eleo 1.0 database will remain accessible after migration, so you can complete this step before or after the transition.
Memberships
What you need to know: In Eleo 2.0, membership levels are being removed, and only membership types will remain. During the data transfer, any existing membership levels within a membership type will convert into standalone membership types. The new name will combine the type and level name, formatted as "(Membership Type) - (Membership Level)."
For example, if you previously had a membership type called "Gym Membership" with levels named "Senior" and "Child," these will become separate membership types, now named:
- Gym Membership - Senior
- Gym Membership - Child
To Do:
No action needed.
Mailings
What you need to know: For a more streamlined experience, the Thank You Template now handles all personalized gift acknowledgments, and the Receipt Template has been removed from Eleo 2.0. As a result, no Receipt Templates or Receipt Mailings will transfer to the new system.
To Do:
☐ Delete templates you no longer need.
☐ Recreate any Receipt Templates as Thank You Templates in Eleo 1.0 that you wish to have transferred to Eleo 2.0.
☐ Copy and paste the content from your Receipt Template into a Thank You Template.
☐ Re-add any previously included fields.
Other Items Not Transferring
What you need to know: Due to upgrades and system improvements, not all data or items can be transferred to Eleo 2.0. However, everything can be added back or recreated as needed. Below is a list of data and items that will not transfer to Eleo 2.0.
- Saved and favorited reports
- Matching gifts
- Calendar tasks
- Web Forms and Web Form submissions
- Integration setup
- Event Groups
Remember: Your Eleo 1.0 database will remain accessible in ‘View Only’ mode after the migration, allowing you to review any items or data that were not transferred.
To Do:
No action needed.
Pro-Tip: Start making a list and prioritizing the items you’ll want to recreate and add back into Eleo 2.0.
Payment Processing
What you need to know: Eleo 2.0 will continue to integrate with Stripe but will no longer support Braintree.
Note: The Braintree integration in Eleo 1.0 will also be discontinued, with the official end date to be
announced. While we recommend switching at your earliest convenience, ample time will be provided for those currently using Braintree with Eleo to sign up with another payment processor.
To Do:
☐ For those using Braintree or without a payment processor: Apply for Stripe so you can integrate as soon as your Eleo 2.0 database is ready.
NOTE: Recurring Gift Accounts from Stripe and EleoPay will be moved over to 2.0.
User Roles & Access
What you need to know: All users will be transferred to Eleo 2.0, but access will depend on their assigned role in Eleo 1.0 at the time of transfer. Custom user roles will not transfer, but they can be recreated in Eleo 2.0. click here to learn more about the Default Roles set up in your new database.
Here’s how database access will work:
- Administrators → Transfer to Administrator role and will stay active with full access.
- All other user roles (active or inactive status) → Transfer to Converted User role and will be set inactive until you activate the user to the appropriate role and assign permissions.
To maintain database security, review your user list to ensure each has the correct role and active
status before the move. Usernames will be replaced with the email address associated with each user account for login.
To Do:
☐ Inactivate unnecessary users.
☐ Review which users have the Administrator role and change accordingly (remember, those users set as the Administrator role will have access to your Eleo 2.0 database immediately after transfer).
☐ Ensure each user’s account has their correct and current email address before the transfer. Update as needed.