We understand the desire to keep your database clean and organised. However, given the importance of maintaining historical data and avoiding the permanent loss of valuable information, it's crucial to understand the implications of deleting profiles, forms, automation workflows, application templates, and other components in your platform. Please consider the following advice to avoid unintended consequences:
Consider the long-term impact: Before deleting any forms, automation workflows, or other elements, think about how this action might affect your historical data. Deleting these components can lead to a fractured track record of your relationship with your leads and applicants, making it difficult to analyse past interactions and measure the success of your nurturing efforts.
Archive instead of delete: If you're looking to declutter or streamline your database, consider archiving old programmes and classes instead of deleting them. This way, you retain access to historical data without cluttering your active workspace.
Enforce naming conventions: For components that cannot be archive, implement clear naming conventions to help differentiate between current and outdated items. For example, labeling outdated forms as “Brochure Request Form (No Longer in Use)” allows you to easily tell legacy data apart from "live data" without confusion.
Backup critical data: Regularly back up your critical data. If you ever need to delete forms, events, or something else of the sort, ensure you export a copy of the data they contain. This precaution can save you from permanently losing valuable information.
Document past work to inform future work: When dealing with components that have complex configurations, such as portal pages with accessibility restrictions and intricate navigation sequences, it’s beneficial to keep some examples of these setups, even if they are no longer in use. This way, you have a reference for replicating similar configurations in the future. Alternatively, documenting these settings and storing the documentation in a shared team drive can serve as a valuable resource for your team. This practice ensures you can efficiently recreate desired results and maintain consistency in your configurations over time.
Review with a team member: Before making any deletions, review the decision with a team member or supervisor. A second opinion can help ensure that the action won’t have unintended negative consequences.
Understand the permanence: Remember that deleting certain elements in our platform is permanent. Make sure you're absolutely certain before proceeding with deletions, as this action cannot be undone.
Reach out for assistance: If you’re unsure about the impact of deleting a particular form, workflow, or whatnot, reach out to our support team or to your Customer Success Manager. We can help you understand the potential implications and advise your accordingly.
By following these guidelines, you can maintain a clean and efficient database while preserving the integrity and continuity of your historical data.