10-Year Legacy Database Sanitization & Archiving Before ERP Migration: Purging Dormant Records

1. The 'Garbage In, Garbage Out' Trap of Cloud ERP Migrations

When an enterprise decides to migrate to modern cloud Odoo ERP, the natural instinct is to import everything: every old customer contact who bought a single spare part in 2014, every obsolete product trial formulation, and every closed ledger entry from the pre-GST VAT/Excise era.

Migrating a decade of dirty data into a new system is fatal. It pollutes the modern ERP from day one. Search dropdowns become cluttered with inactive vendors, duplicate customer records cause credit limits to be fragmented, and database indexing performance degrades. A clean break is required.

2. The 3-Tier Data Sanitization & Archiving Strategy

Our data hygiene protocol classifies legacy records into three rigorous tiers:

• Tier 1: Active Working Master (Migrate to Odoo): Active customers, approved vendors, current catalog products, open purchase/sales orders, and audited opening financial balances.
• Tier 2: Cold Compliance Archive (S3 / Parquet Lake): Detailed transaction rows from 2015-2023 stored in compressed, read-only Parquet format queryable via DuckDB/Athena for statutory tax audits.
• Tier 3: Obsolete Scraps (Permanent Purge): Duplicate vendor drafts, abandoned quotation inquiries, and unlinked temp logs.

3. Production Odoo 19 Python ORM Data Sanitization Blueprint

Below is the Odoo model enforcing active transaction verification before allowing partner import:

# -*- coding: utf-8 -*-
from odoo import models, fields, api, _

class LegacyPartnerSanitizer(models.TransientModel):
    _name = 'legacy.partner.sanitizer'
    _description = 'Pre-Migration Data Cleansing Assistant'

    def action_filter_active_partners(self, staging_record_ids, cutoff_years=3):
        """
        Filters staging partner records: only partners with transactions
        within cutoff_years are marked for live Odoo migration.
        """
        StagingModel = self.env['legacy.migration.staging']
        staging_records = StagingModel.browse(staging_record_ids)

        approved_ids = []
        archived_count = 0

        for rec in staging_records:
            # Parse last transaction date from payload
            import json
            data = json.loads(rec.raw_payload_json or '{}')
            last_date_str = data.get('last_tx_date')

            if last_date_str:
                last_dt = fields.Date.from_string(last_date_str)
                years_ago = (fields.Date.today() - last_dt).days / 365.25
                if years_ago <= cutoff_years:
                    approved_ids.append(rec.id)
                    continue

            # Mark as cold archive
            rec.write({
                'migration_status': 'failed',
                'error_log': f"Dormant: No transaction in last {cutoff_years} years. Sent to Cold Archive."
            })
            archived_count += 1

        return {
            'approved_for_migration': len(approved_ids),
            'archived_count': archived_count
        }

4. Statutory Tax Audit Readiness

Indian tax law requires maintaining accounting books for 8 previous financial years. By preserving legacy databases in encrypted, immutable cloud archives, the company remains 100% compliant for GST assessments and Income Tax scrutiny while keeping the live Odoo ERP fast and lean.

5. Implementation & Clean Go-Live

Sanitizing your database before migration eliminates clutter, boosts employee productivity, and ensures your new cloud ERP launches with pristine data integrity.