Data Migration - From ACS


Data Mapping Chart  - What is included and what is not
Process Overview
Detailed 3 Step Process 
How to Delete Inactive Records

ACS to Elexio Community Data Migration Mapping Chart

Items with a “-” are items that do not migrate. 

This is subject to change if ACS changes their system, version or method of providing the data files we normally use.



Custom Fields

- (Because of the ACS data structure, no custom
fields can be migrated. However, you can import
the data in those fields in mass using the Import People
feature on the Data Migration FAQ page. You can
practice after your initial migration, but will need to do
the import again after you sign-off on your final data migration.) 

Family position

Relationship (Head would default to primary)



First Name

First Name

Middle Name


Goes By

Preferred Name

Last Name

Last Name


Appended to the last name field



Date of Birth

Born On

Marital Status

Configurable Text Field

Address Line 1


Address Line 2






ZIP Code

Zip Code



Home Phone

Home Phone (Only one per person)

Mobile Phone

Cell Phone (Only one per person)

Work Phone

Work Phone (Only one per person)


Primary (Also Secondary Email if one exists)


Created Date

Last Attended Date

Last Attended Date





Activity, Class, Lists



*Groups (and Configurable Text Field for
reference and for using Advanced Search to
populate the Status groups if needing
additional combining or detail). We
recommend using groups for Status going
If the Status value is Member, the join date will be
added as the join date of the Member group. If there is
not a join date in ACS, the migration date will be saved as
the Join Date in Community for this Member group. If there 
is not a status value of Member, the join date will not
be added to any statuses. 

Status Date

Group Join Date

Envelope #

Envelope #

Date Joined

Configurable Date Field

Joined How

Configurable Text Field


 - (Not migrated because the systems track it so differently on the back-end. One option is to enter attendance manually for the current semester since it is the most important for tracking who is present to help in their discipleship and assimilation. Also current semester data is most important for tracking who is absent to keep them from falling through the cracks. Of course this would need to be done once the conversion has your final sign-off.)





Active Fund

Contribution Amount


Date Received


Check Number

Check Number



Pledge Frequency


Unmatched Contributions






*Customized group name


*Customized group name


*Customized group name

* indicates automatic configuration may occur to provide appropriate destination fields for incoming data. 

Activity Name examples:

  • ACTIVITY - Group - Category - List 1 - List 2 - List 3
    • ACTIVITY - Youth Ministry - Children’s Ministry - Kids Town - 10AM - Nursery
    • ACTIVITY - Services - Church Wide Services – Weekend – Sun 9AM - Attendance

Just so you are aware... Are you considering using the Import People (and Import Giving) feature instead of the Data Migration to add all your people and giving? If so, note that Family relationships are not able to be imported, so you will have to attach all your people back into families manually.

Typical Migration Process Overview

  • You upload a copy of your data to our secure DropBox folder 
  • We program your migration and migrate your data into Elexio Community. This may take some back and forth communication.
  • You review the migration of the data.
  • You communicate to us any issues you find.  
  • You select a date for your final migration and confirm with us - with the advice of your Success Coach if you have one.
  • When that time comes, we run your final migration.
  • You review and sign-off on the final migration, then start using Community

Successful migration requires deliberate collaborative efforts by both Elexio and you. Migration occurs in phases to allow time for you to validate your data. Your Data Champions Team should be included in the process of validation and training, rather than just informed when the data migration is complete.

 Back to Top

Detailed 3 Step Process

  1. Initial Data Migration

The first run of data migration into Elexio Community is called Initial Data Migration (IDM). On your scheduled IDM Date, an initial migration is performed. The IDM does not change or delete information in your current system.

Once you’ve been notified that your IDM has been completed, you and your team will begin verifying data accuracy. First, you will verify that your data has been migrated accurately by comparing what migrated into Community versus what is recorded in your current system. Please complete this data validation before making any changes in Elexio Community. You will need to review any automatic system configurations created in the IDM process. The validation effort will ensure accuracy and complement your other training efforts.

Even though you see your data in Elexio Community, you will continue using your current system until your Final Data Migration is complete. Even if your data migration mapping choices have been finalized, we recommend taking the time to learn Community, making implementation decisions, testing, and preparing your team before you complete a Final Data Migration and go live.


  1. Sandbox Phase

After initial data migration and subsequent adjustment migration runs, a copy of your data remains temporarily in Elexio Community. On a later date, when the final data migration is run, all the data in Elexio Community will be purged and replaced with the most current data from your current system. The time between these two dates provides a "sandbox" training environment in Elexio Community during your implementation process. The Sandbox Phase is an ideal time to practice using Community and defining your processes.

We recommend 4 to 16 weeks of learning and planning before going live. The average church goes live in the 8 to 10 week range.

You can practice in Elexio Community with your own data and practice entering new data without risk. During the Sandbox Phase, please remember to only enter data into Elexio Community for practice, as all data and configurations will be purged from Elexio Community on a later date.


  1. Final Data Migration (FDM) and Go Live

After taking the time to learn Community, making implementation decisions, testing, and preparing your team, a final data migration to Elexio Community can be executed. The scope of migrated data and configuration is the same as Initial Data Migration. FDM purges all data from Elexio Community and replaces it with a copy of the most recent data you upload. FDM does not remove or delete data from your current system. You can save it or export it as an archive copy in case you need it later. 

This is the moment your church ceases to use your current system and begins to use Elexio Community exclusively. During the review period of this final run, you should not edit either database between the final data migration and your final sign-off. Please consider the impact of this change carefully. You will want to have planned accordingly and be ready to communicate with your staff, volunteers, and congregation as desired. 

Successful churches pre-schedule their FDM to occur at the end of their team’s implementation planning process, just before the team switches to Elexio Community. Here is the schedule surrounding FDM:

  • All data entry must be completed in your current system prior to data migration.
  • Both your current system and Elexio Community must be left idle on the day(s) of migration.
    • Elexio Community will be ready for validation immediately following migration.
    • We recommend that you validate your data in Elexio Community compared to your current system data, just as you did after the Initial Data Migration. If you see any discrepancies, please contact Elexio with a detailed explanation of what information was not imported correctly, allowing us to make corrections as quickly as possible.
  • After validation, you sign-off, then we give you the go-ahead for your team to begin using Elexio Community to complete any additional setup and data entry in preparation for Go Live.

Go Live

Once your Final Data Migration is complete and your data validated, you will announce to your team that your church is now Live with Elexio Community. It is at this point that Elexio Community becomes your authoritative database. From this day forward your team will use Elexio Community for all data management.

Here are a few things you’ll want to do right after your FDM is signed off on:

  • Assign correct permission roles to all needed users
  • Check and update settings if needed
  • If you are using Elexio Giving, follow these instructions or this step by step guide to integrate Elexio Giving with Elexio Community.
  • Start data clean up if necessary (edit, merge, move, split, etc.)
  • Set up groups by changing names, adding groups, and adding members and leaders to groups or deleting unneeded groups
  • Check all group settings and create and assign group Categories and Properties
  • Setup any needed Interaction types, workflows, etc.

 Back to Top 

How to Delete Inactive Records

Be very careful. One of the biggest risks is deleting records with current year giving and not being able to send them giving statements.

In Community, you can view a list of everyone in a group and then delete them all or just check certain names from the group and delete them in mass. However, there is not a field in Community for Last Contributed by Household, so it is very risky to delete people in mass without deleting people with contributions.

One option is before your final data migration, create a Group, Mailing List, or set a field value that is being migrated in your current system if you have the ability to do so then delete all the people in the Group, Mailing List, or with that field value in Community after the final conversion.  

Typical Steps to delete records:

  • Create a Mailing List or new Group that you know is part of the migration such as “TEMP - Inactive Records to be Deleted.”
  • Filter the individuals in your database using the criteria you determine important such as Last Contributed and/or Last Attended. You want to make sure you are not deleting anyone who has current year giving, so include the Last Contributed by Household field if one is available.
  • Example filters:
    • Status is something like No Longer Attending AND Last Contributed by Household is less than 1/1/2016 (or less than 1/1/2017 depending on how many records you want to delete).
    • Custom Search if you have the ability to do this: Using filters similar to Status of Inactive or No Longer Attending or Giving.
  • Be very careful, because people in the same household may have different statuses and you could end up deleting just the parents or just the children.
  • Once the list is checked and finalized, then add the individuals to the Mailing list or Group you created for this purpose.
  • To double-check your new Groups, Mailing List, or field, run a Contribution report in your current system to verify that none of them have current year contributions or a current status.
  • In Community:
    • Run a Giving report that filters for people in the Group or Mailing List to verify that none of them have current year contributions.
    • Click on Groups, then click the group to be deleted.
    • Click the check all box at the top left to select everyone in the group.
    • Click the gear and select Delete People From Entire System and click OK to all the prompts.
    • Delete the temporary group itself (it should be empty now).

Before your final conversion, we recommend thorough testing in at least one of your interim runs to make sure you didn’t accidentally delete records with giving. After you review the interim conversion run for overall data accuracy and there is nothing needing to be fixed, test the deletions. First, delete the records using the above steps, then run reports for current year giving totals in both Community and your current system to make sure they match.

 Back to Top