CRM maintenance and replacement

Maintain a CRM by finding recurring problems in customer work, fixing their causes and checking whether the fixes hold. Consider replacement when an essential task remains unsupported after a defined repair assessment, or when the continuing effort to make it work is unjustified. An untidy screen alone does not establish a need to switch.

Keep a maintenance register

For each recurring problem, record the affected task, an example record, its owner and the next decision. Separate unclear business rules, incorrect data, configuration, access and product limits. This stops a replacement project carrying the same problem into a new system.

Review the register when the sales process, team or connected systems change. Give unresolved items a decision owner.

Use inactivity as a review trigger

Pipedrive lists no activity or updates for 6–12 months, with no upcoming tasks or expected follow-ups, as a common reason to consider archiving a deal or lead. Treat this as a prompt to review the record, not a universal expiry rule: confirm whether a customer decision is still pending and whether the work remains active.

Other Pipedrive examples include lost deals or cold leads that will not be revisited, delivered and completed won deals, disqualified leads, and low-priority records from past campaigns or experiments. It also identifies records kept for compliance, audits or reporting as possible candidates when they need not remain visible in the main workspace.

Pipedrive automations can use archive status as a condition or action, including to archive stale records after a period of inactivity. The feature is available on Advanced and higher plans; one example is archiving won or lost deals with no updates in 90 days. Check that this rule matches the organisation's review practice before enabling it.

Key CRM Maintenance Metrics

Clear active work while keeping useful history

Decide what an older opportunity represents before hiding it. A completed deal may belong in history; an open deal with a credible customer decision pending still needs an owner and review point. Keep the outcome, customer relationships and relevant commitments findable for as long as there is an approved purpose to retain them.

The method depends on the CRM. Pipedrive's deal archive keeps a deal's open, won or lost status and makes it available in its Archive tab. Archived deals retain that previous status, and the archive change can trigger configured automations or webhooks.

HubSpot's saved deal views can filter records to create reusable displays; filtering does not itself archive a record or set a retention period. Check reporting, integrations and retrieval before changing many records.

For organisations subject to the Australian Privacy Principles, an archive still needs a personal-information retention assessment. APP 11 requires reasonable steps to destroy or de-identify personal information no longer needed for a permitted purpose, subject to its stated exceptions. A deal's commercial history may have a different answer from personal details in its notes and copies.

Pipedrive vs HubSpot: Archive and Export Capabilities

Keep archived work retrievable

In Pipedrive, archived deals remain accessible through the Deals list's Archive tab and as linked items in people, organisations, activities, projects, the sales inbox, products and hover cards. Staff can find historic context from the related customer or work item, rather than relying only on a separate archive list.

Check the limits on retaining personal information

The OAIC explains that APP 11.2's destruction or de-identification requirement does not apply to personal information in a Commonwealth record, or where an Australian law or a court or tribunal order requires retention. The OAIC also identifies technical and organisational measures as part of reasonable steps, so retention decisions need to account for how information is protected as well as whether it is still needed.

Simplify configuration with a purpose

Start with a field or rule that causes a real problem. Ask who enters its value, who uses it and what would fail if it changed. Check forms, reports, workflows, imports and integrations before hiding or deleting it.

These controls reveal technical use, not whether the business still needs the information. Make a limited change, inspect the affected customer task and record the decision.

Use property groups and definitions during review

HubSpot property groups can organise related properties within an object, making them easier to find in settings. They do not appear on the record itself; record sidebars group properties on a record.

Archiving a HubSpot property requires Edit property settings permission. HubSpot allows archiving a property not used in records or assets such as segments, index pages or report filters. Property-definition exports can help identify outdated or redundant properties.

Decide the next route

Describe the essential outcome the CRM fails to deliver. Establish whether supported configuration or a process change can provide it with acceptable ongoing effort. If a material gap remains, assess replacement with the required record relationships, history, access, integrations, training and transition work in scope.

A record export is only part of that assessment. HubSpot's standard record export contains current property values and associations, but its default selection follows the chosen view and contact activities need separate routes. Pipedrive says linked activities, notes and files require separate exports.

Specify what must remain accessible before treating an export as a migration plan.

Record one of three decisions: repair a defined problem, assess replacement against a remaining gap, or hold the decision until a material uncertainty has an owner and answer.

If you review Pipedrive export options as part of a replacement assessment, check who can export and what they can see. Global admins and users with the required permissions can export, but users are limited to data visible under their visibility group or item visibility. Exporting by data type is available only to global admins.