What is field archiving?
The field archiving feature helps you maintain governance and organization in your Pipefy forms. You can hide fields that are no longer used without losing the historical data they contain.
Why archive a field?
Archiving is a safe alternative to permanently deleting a field.
Unlike deleting, which removes the field and its data entirely, archiving simply deactivates the field while keeping it available for read-only and history purposes.
This feature is especially useful when:
You're not sure whether the field will be needed again in the future.
The field contains relevant information that must be kept for historical purposes.
The field is outdated due to process changes, but its history is still important for read-only settings.
How to archive a field
In the pipe form editor, whether it's the start form or phase form, click the three-dot icon next to the field you want to archive. Select the Archive field option.
Confirm the action in the confirmation dialog.
What happens after archiving?
The field will no longer appear in forms or cards and cannot receive new values.
The field can still be selected and used as a read-only value in automations, AI agents, conditionals, reports, and interfaces.
Any instances that depend on this field to write or modify its value will cease to function until the field is replaced.
The field remains visible in Field Dependencies, making it easier to identify and replace where it's still being used.
To verify if a form has archived fields, use the new filter.
How to restore an archived field
If you need to use the field again, go to the form editor.
Use the "Archived" option to filter the form.
Click the three-dot icon next to the field you want to restore. Select the Restore field option. The field will be fully restored.
Best Practices
Before archiving, use the Field Dependencies tool to check where it is used.
Prefer archiving over deleting when the field has relevant historical data.
If you need to discontinue the use of several fields, archive them gradually to avoid impacting critical automations.