Learn how PloverCRM’s cascade rename feature automatically updates stage names across all contacts when you rename a stage.
Overview #
When you rename a contact stage in PloverCRM, the system automatically updates the stage name for all contacts currently in that stage. This “cascade rename” feature ensures consistency across your entire contact database without manual updates.
How Cascade Rename Works #
Automatic Updates #
When you rename a stage:
- The stage definition is updated with the new name
- All contacts currently in that stage are automatically updated
- Historical stage data is preserved
- The stage slug remains unchanged (for API compatibility)
What Gets Updated #
- Stage Name: The display name shown throughout the interface
- Contact Records: All contacts in that stage show the new name
- Filters: Stage filters reflect the new name
- Reports: Analytics and reports use the new name
- Mobile App: The mobile app syncs the new stage name
What Doesn’t Change #
- Stage Slug: The internal identifier remains the same
- Stage Color: Color settings are preserved
- Stage Order: Position in the pipeline doesn’t change
- Historical Data: Past stage transitions are preserved
- API References: API calls using the slug continue to work
Renaming a Stage #
Via Settings Page #
- Navigate to PloverCRM > Settings
- Click on the PloverCRM tab
- Scroll to the Stages section
- Find the stage you want to rename
- Click the Edit button or click on the stage name
- Enter the new name
- Click Save or press Enter
The system will automatically update all contacts in that stage.
Via Inline Edit #
Some views allow inline editing:
- Navigate to the stages management area
- Click directly on the stage name
- Type the new name
- Press Enter or click outside to save
Confirmation #
After renaming, you’ll see a success message:
“Stage renamed successfully. X contacts updated.”
This confirms how many contacts were affected by the rename.
Use Cases #
Rebranding Pipeline Stages #
When your sales process evolves:
- Old: “Lead” → New: “Prospect”
- Old: “Opportunity” → New: “Active Deal”
- Old: “Customer” → New: “Client”
All contacts automatically reflect the new terminology.
Clarifying Stage Names #
Make stages more descriptive:
- Old: “New” → New: “New Inquiry”
- Old: “Contacted” → New: “First Contact Made”
- Old: “Qualified” → New: “Qualified Lead”
Fixing Typos #
Correct mistakes without losing data:
- Old: “Negotation” → New: “Negotiation”
- Old: “Propsal” → New: “Proposal”
Localization #
Translate stages to different languages:
- Old: “New” → New: “Nouveau” (French)
- Old: “Won” → New: “Gewonnen” (German)
Best Practices #
Plan Before Renaming #
- Communicate changes to your team before renaming
- Document the reason for the rename
- Consider the impact on reports and integrations
- Check if external systems reference the stage name
Maintain Consistency #
- Use consistent naming conventions across stages
- Keep stage names concise (2-3 words maximum)
- Use action-oriented names when possible
- Avoid abbreviations that might be confusing
Test First #
- If possible, test the rename in a staging environment
- Verify integrations still work after renaming
- Check that reports display correctly
- Ensure mobile app syncs the new name
Document Changes #
- Keep a changelog of stage renames
- Update team documentation and training materials
- Notify team members of the change
- Update any external documentation or wikis
Technical Details #
Database Updates #
When you rename a stage, PloverCRM:
- Updates the stage definition in
wp_options - Queries all contacts with the old stage name
- Updates the stage meta field for each contact
- Maintains the stage slug for API compatibility
Performance Considerations #
- Renaming stages with many contacts may take a few seconds
- The operation is performed in a single database transaction
- No data loss occurs during the rename process
- The system handles large contact databases efficiently
API Compatibility #
The stage slug (internal identifier) never changes, ensuring:
- API integrations continue to work
- Mobile app syncs correctly
- Webhooks and automations aren’t affected
- Historical data remains consistent
Troubleshooting #
Rename Doesn’t Apply to All Contacts #
Problem: Some contacts still show the old stage name after renaming.
Solutions:
- Refresh the page (Ctrl+F5 or Cmd+Shift+R)
- Clear WordPress cache if using a caching plugin
- Check if those contacts were moved to a different stage
- Verify the rename operation completed successfully
Error During Rename #
Problem: An error message appears when trying to rename a stage.
Solutions:
- Check for duplicate stage names
- Verify you have permission to update settings
- Ensure the new name isn’t empty
- Check for special characters that might cause issues
- Try a different browser
Mobile App Shows Old Name #
Problem: The mobile app still displays the old stage name.
Solutions:
- Force sync the mobile app (pull to refresh)
- Log out and log back in to the mobile app
- Check mobile app version (update if needed)
- Verify the rename was successful in the web interface
Reports Show Inconsistent Data #
Problem: Reports display both old and new stage names.
Solutions:
- Refresh the report
- Clear report cache if applicable
- Regenerate the report
- Check if the report is using historical data
Comparison: Rename vs Delete & Recreate #
Cascade Rename (Recommended) #
Pros:
- Preserves all contact data
- Maintains historical records
- No data loss
- API compatibility maintained
- Quick and easy
Cons:
- Can’t change the stage slug
- All contacts are updated (can’t keep some with old name)
Delete & Recreate (Not Recommended) #
Pros:
- Can create a new slug
- Fresh start
Cons:
- Contacts in deleted stage are moved to default stage
- Historical data may be lost
- API integrations may break
- More complex process
- Risk of data loss
Recommendation: Always use cascade rename unless you absolutely need to change the stage slug.
Related Articles #
- Managing Stages
- Stage Deletion Protection
- Stage Colors Customization
- Contact Stages Overview
- Stages API
FAQ #
Q: Will renaming a stage affect my API integrations?
A: No. API integrations use the stage slug (internal identifier), which doesn’t change when you rename a stage. Only the display name changes.
Q: Can I undo a stage rename?
A: Yes. Simply rename the stage back to its original name using the same process. All contacts will be updated again.
Q: How long does it take to rename a stage with many contacts?
A: Typically a few seconds, even with thousands of contacts. The operation is optimized for performance.
Q: Will historical stage transitions be affected?
A: No. Historical data is preserved. Only the current stage name is updated for contacts currently in that stage.
Q: Can I rename multiple stages at once?
A: No. Stages must be renamed one at a time to ensure data integrity and provide clear feedback.
Last Updated: February 3, 2026
Applies To: PloverCRM 2.0+
