Skip to main content

How to Sync Parent and Child Accounts with Grow Sub-Account Fix

How sub-account sync works, what changed, and how to verify your setup is configured correctly.

Written by Jessica Hamel

Overview

The Grow Sub-Account Fix allows gyms with family memberships to sync parent and child accounts into Grow without broken contacts or missing communication. This article explains how sub-account sync works, what changed, and how to verify your setup is configured correctly.

Why Use Grow Sub-Account Sync?

  • Clean sync for every member — Parent and child accounts sync without overwriting each other or failing mid-process.

  • No extra setup required — Proxy emails are generated automatically behind the scenes. There is nothing for staff to configure per member.

  • Supports real-world gym workflows — Family accounts, martial arts programs, and youth memberships work the way gyms actually run them.

  • Preserves communication flow — Messages still reach the right person. Parents receive and reply to Grow messages as normal.

  • Removes a key adoption blocker — Gyms that previously skipped sub-account sync due to failures can now fully use Grow.

What's New

  • Sub-accounts now get a unique proxy email — Each child or sub-account receives a system-generated address (example format: u.{token}@inbox.pushpress.com) so Grow treats them as separate contacts.

  • Smart email routing — Emails sent to proxy addresses are intercepted and forwarded to the parent's real email. Reply routing back into Grow is preserved.

  • Safe sync behavior — This update only creates new contacts. It does not overwrite or modify existing ones.

  • Phone number protection — If a sub-account shares a phone number with the parent account, the phone number will not sync to prevent Grow from merging those contacts.

  • Who has access: All Grow customers. No plan upgrade required.

  • Configuration requirement: "Allow Duplicate Contacts" must be turned off in Grow for this to function correctly.

How to Set Up Grow Sub-Account Sync

1. Confirm Your Grow Duplicate Contact Setting

To confirm your Grow duplicate contact setting, log into your Grow account and navigate to Settings. Locate the "Allow Duplicate Contacts" option and verify it is turned off. If this setting is enabled, sub-accounts may not sync correctly.


2. Verify Sub-Account Sync in PushPress

To verify sub-account sync in PushPress, open your PushPress Core admin and navigate to the Grow Sync settings. Confirm that Grow Sync is active and that your member accounts include family or sub-account relationships. No additional configuration is needed to enable the proxy email feature.


3. Test a Sub-Account Sync

To test a sub-account sync, locate a member with an existing parent or child account relationship. Trigger or wait for the next sync cycle. In Grow, confirm the sub-account appears as a separate contact and that the parent contact is unchanged.


How to Use Grow Sub-Account Sync

  1. Add or update a member with a parent or child account relationship in PushPress Core.

  2. Allow the sync to run (automatic on the next sync cycle).

  3. In Grow, confirm the sub-account contact exists and is listed separately from the parent.

  4. Send a test message from Grow to the sub-account contact and confirm the parent receives it.

  5. Reply from the parent's email and confirm the reply appears in the correct Grow conversation thread.

Troubleshooting Grow Sub-Account Sync

If sub-accounts are not syncing into Grow, check the following:

  • "Allow Duplicate Contacts" is turned off in Grow (this is required)

  • Grow Sync is active in PushPress Core

  • The sub-account has a distinct email address (shared emails will not sync)

  • The sub-account does not share a phone number with the parent (shared phone numbers are excluded by design to prevent contact merging)

Still stuck? Try logging out and back in, refreshing the page, or testing on another device. Contact PushPress Support if the issue persists after verifying all settings.

Important Notes

Important: This update applies to new sub-account syncs going forward. It does not retroactively fix existing contacts that were previously overwritten or failed to sync. Migration options for existing contacts may be available later.

Note: Sub-accounts that share a phone number with the parent account will not have the phone number synced to Grow. This is intentional and prevents contact merging in Grow.

Note: "Allow Duplicate Contacts" must be turned off in Grow. If this setting is on, the proxy email system will not work as expected.

Frequently Asked Questions

How does the sub-account fix handle parent and child accounts in Grow?

The sub-account fix handles parent and child accounts by assigning a unique proxy email to each sub-account so Grow treats them as separate contacts. All communication from Grow still goes to the parent's real email, so nothing changes for the member.

Will anything change for my members or parents?

No, nothing will change for your members or parents. Parents still receive and reply to messages as normal. The proxy email is handled entirely behind the scenes and is not visible to members.

Do I need to set anything up to enable this?

You do not need to set anything up beyond confirming that "Allow Duplicate Contacts" is turned off in Grow. The proxy email generation is automatic.

Will this affect my existing contacts in Grow?

This update will not affect your existing contacts in Grow. It only applies to new sub-account syncs and will not overwrite or modify contacts that are already in Grow.

What happens if a sub-account shares a phone number with the parent?

If a sub-account shares a phone number with the parent, the phone number will not sync for that sub-account. This prevents Grow from merging the two contacts. The sub-account will still sync with its proxy email.

Does this fix past sync failures for my existing sub-accounts?

This update prevents new failures but does not automatically fix past sync issues. Contacts that previously failed to sync or were overwritten will need to be reviewed manually. Migration options may be available in the future.

Did this answer your question?