Acquisition Software Architecture Harmonization Checklist

Role: Enterprise Technology Integration Director experienced in post-merger software consolidation and technical due diligence execution.

Context

• Acquired company: {{acquired_company_name}}
• Parent platform: {{parent_platform_name}}
• Primary integration goal: {{primary_integration_goal}}
• Compliance framework: {{compliance_framework}}
• Integration timeframe: {{integration_timeframe}}
• Critical shared services: {{critical_shared_services}}

Task

Create a comprehensive technical alignment checklist to systematically evaluate, govern, and merge the software architectures of {{acquired_company_name}} and {{parent_platform_name}} according to {{compliance_framework}} standards within {{integration_timeframe}}.

Method

1. Map overlapping technical capabilities between {{acquired_company_name}} and {{parent_platform_name}} relative to {{primary_integration_goal}}.
2. Inventory software licenses, proprietary libraries, and third-party dependencies to flag intellectual property and licensing exposure.
3. Audit access management, data governance, and cryptographic practices against {{compliance_framework}} specifications.
4. Design boundary interface checks to securely connect {{critical_shared_services}} like auth, logging, and billing.
5. Detail infrastructure standardization checkpoints including CI/CD pipelines, container registries, and telemetry ingestion.
6. Formulate phased integration milestones distributed across {{integration_timeframe}} to manage technical debt accumulation.
7. Assign a risk rating (High, Medium, Low) and responsible functional lead to every harmonization task.

Constraints

• MUST categorize every checklist item under an architectural domain (Security, Infrastructure, Data, Governance, Engineering).
• MUST tag each checklist item with an explicit Risk Severity rating (High/Medium/Low).
• MUST NOT recommend immediate full-codebase rewrites; prioritize pragmatic bridging, encapsulation, and incremental alignment.
• Focus strictly on technical architecture, systems interoperability, and security governance.

Output format

• Section 1: Harmonization Objective & Scope (1 brief paragraph aligning the checklist to {{primary_integration_goal}}).
• Section 2: Phase 1 (Days 1-30) — Baseline Audit & Security Discovery Checklist (6-8 domain-categorized items with risk ratings).
• Section 3: Phase 2 (Days 31-90) — Shared Services & Interoperability Checklist (6-8 items targeting {{critical_shared_services}}).
• Section 4: Phase 3 (Final Phase) — Platform Convergence & Policy Harmonization Checklist (4-6 items completing {{integration_timeframe}} goals).
• Section 5: Critical Architectural Risks & Blockers Watchlist (3-4 high-severity integration risks).

Self-review

1. Are all 6 variables ({{acquired_company_name}}, {{parent_platform_name}}, etc.) contextualized across all phases?
2. Does every item include both a defined architectural domain and a risk severity rating?
3. Does the checklist respect {{compliance_framework}} compliance requirements throughout?