Copy or move a member between choirs

Transfer a member from the children's choir to the main choir or between sibling choirs — address, IBAN and master data come along, voice part matched automatically.

Web
ChöreChor öffnenMitgliederKopieren / Verschieben

Diese Funktion ist nur im Web verfügbar.

Permission required: Members › Edit
✉ Sends email

What is this?

When a member moves from one of your choirs to another — typical case: from the children''s choir to the main choir — you do not have to create them twice. With Copy or Move you carry over the master data in one click. Saves typing and avoids errors on IBAN or address.

Copy vs. Move — when to use what?

  • Copy — the member sings in both choirs (e.g. children''s choir and main choir at the same time).
  • Move — the member switches completely (e.g. has grown out of the children''s choir).

How to do it

  1. Open the source choir and go to Members.
  2. Click the arrow icon (horizontal double arrows) on the desired member — the button only appears for choirs that have sub-choirs or projects.
  3. Pick the mode at the top: Copy (blue) or Move (red).
  4. Choose the target choir from the list of related choirs.
  5. For Move also tick the confirmation checkbox ("Yes, remove … and move them to …").
  6. Confirm with the button at the bottom.

On Copy, the member receives an invitation email for the new choir and stays in the source choir.

On Move, the member is created in the new choir and at the same time removed from the active list of the source choir. Active functions in the source choir are ended with today''s date — historical data stays untouched.

Which choirs are eligible as a target?

Only related choirs are shown:

  • the parent choir (if your current choir is a sub-choir),
  • sibling sub-choirs (other sub-choirs of the same parent choir),
  • your own sub-choirs.

Projects are not allowed as a target — projects sync their members through their own import from the parent choir.

In addition, only choirs where you hold the members.edit permission are shown. Missing permission or an existing membership is listed in a grey note below.

What is carried over?

Field Carried over?
Name, email Yes (same user)
Address, ZIP, city Yes
Phone, mobile Yes
Birthday, wedding anniversary Yes
Entry date Yes
IBAN, SWIFT Yes
Notes Yes
Voice part Yes, if name matches
Role Set to "Member"
Permission group Default group "Member"
Choir function No, fresh "Member" function in target
Custom fields Yes, if field name exists in target
RSVPs, sheet music, ledger No (stay in source choir)

Tips

  • Children''s choir → Main choir: use Move when the change is permanent. Past singer history stays in the children''s choir, but the member does not show up twice in the current member count.
  • Check voice part: if the voice group names differ (e.g. "Soprano I" vs. "Soprano"), the voice will not match. You can assign it manually in the target choir afterwards.
  • For projects: use the project''s "Import members from choir" button instead — it has a dedicated sync mechanism that pulls in master-data changes from the parent choir automatically.

Frequently asked questions

What is the difference between copying and moving?
When **copying**, the member stays in the source choir and is additionally added to the target choir. When **moving**, the member is removed from the source choir — historical data like events, sheet music and ledger entries stay there.
Why can I not pick a project as the target?
Projects pull their members directly from the parent choir via sync import. A manual copy would be overwritten by the sync. Use the project's built-in "Import members from choir" button instead.
Which data is carried over?
Address, phone, mobile, birthday, wedding anniversary, entry date, IBAN, SWIFT and notes. Voice part is matched by name (e.g. "Soprano" → "Soprano"). Role is set to "Member", custom functions from the source choir are not migrated.
What happens to RSVPs, sheet music assignments and ledger entries in the source choir when moving?
They stay there in full. The member only disappears from the active members list — all historical traces of the membership remain for annual reports and statistics.
What happens to custom fields?
Custom fields are carried over when a field with the **same name** exists in the target choir. If no matching field exists, no new field is created in the target — the value is skipped. You can create the custom field upfront in the choir settings so it gets matched during copy/move.
Which permission do I need?
You need the **members.edit** permission in **both** choirs — source and target. If you only have it in one, the other choir does not show up in the picker.

Still have a question? Ask the AI help bot.

Click the help button in the bottom right and ask your question.