msa import congregations msa
Use this importer when you receive a Congregations database from another Meeting Schedule Assistant coordinator. It lets you quickly add all congregations from an exported MSA XML file into your own database.
- Imports congregation records from an MSA XML file
- Adds all congregations found in the file
- Shows how many congregations were imported
- Displays the log file if an error occurs
This importer does not provide mapping options, preview screens, or overwrite settings. It simply reads the file and imports the congregations.
This importer does not use a CSV file.
It requires a Congregations XML file created using the Export feature in Meeting Schedule Assistant.
If you need to create one, see:
When you import a congregation from an MSA XML file, the importer brings in all congregation data, including:
- Congregation information
- All associated speakers
- Speaker privileges and talk outlines
- Memo fields
- Talk Coordinator details
This is a complete import of the congregation as it existed in the original Meeting Schedule Assistant database.
Import → Congregations → From MSA
Figure 1: Selecting the MSA importer.
Go to Congregations → Import from MSA.
When prompted, browse to the XML file you received from another coordinator.
- If congregations were imported, a message shows how many were added.
- If an error occurs, the log file opens so you can review the details.
During the import process, if any congregation names duplicate those already in the database, the importer will append a unique number to the name of the new congregations to avoid conflicts.
The MSA importer provides a quick way to bring congregation data from another Meeting Schedule Assistant installation into your own database. It supports:
- Importing all congregation records from the XML export
- Preserving congregation names and associated metadata
- Automatically adding any congregations that do not already exist
After processing the file, a summary report shows how many congregations were imported. Any errors encountered during the process are written to the log file.
Back to Congregation Importers