inRiver to Blower Migration - Requirements Overview
Project: inRiver PIM Integration
Date: 2026-03-03
Status: Phased Approach
Two-Phase Strategy
Phase 1: Fast Track (2-3 days)
Goal: Get inRiver working with existing Blower infrastructure
Approach: Python converter transforms inRiver JSONL → Heiler CSV format
Details: Phase 1 Requirements
Timeline: 2-3 days
Risk: Low
Value: Immediate inRiver integration
Phase 2: Full Modernization (4-6 weeks)
Goal: Replace Blower with modern dbt + PostgreSQL pipeline
Approach: Bronze → Silver → Gold → Export architecture
Details: Phase 2 Requirements
Timeline: 4-6 weeks
Risk: Medium
Value: Long-term maintainability, sets precedent for modernization
Decision Rationale
Why Two Phases?
- Speed: Need inRiver working quickly (business urgency)
- Risk: Phase 1 is low-risk, proven pattern
- Learning: Phase 1 buys time to understand inRiver data
- Strategy: Phase 2 modernizes Blower for long-term maintainability
Phase 1 Benefits:
- ✅ Minimal code (~500 lines Python)
- ✅ No infrastructure changes
- ✅ Blower handles everything else
- ✅ Can deploy in days
Phase 2 Benefits:
- ✅ Modern data stack (dbt + PostgreSQL)
- ✅ Better performance and scalability
- ✅ Sets precedent for replacing other Blower sources
- ✅ Easier to maintain and extend
Current Status
Phase 1: Requirements complete, ready for approval
Phase 2: Requirements documented, deferred until Phase 1 stable
Next Steps
- Review Phase 1 requirements
- Approve Phase 1 approach
- Build Python converter
- Test and deploy Phase 1
- Plan Phase 2 timeline
Document Version: 1.0
Last Updated: 2026-03-03
Author: AI-DLC Requirements Analysis