egbim_qa_platform/scripts/generated/egbim_migration

EGBIM QA migration artifacts

These files are generated from scripts/egbim_qa.sql; the source dump itself is not a target migration script.

Files

• userfeedback_feedbacks.sql: inserts the 427 legacy posts into ABC userfeedback.feedbacks on EGBIM channel 2. Migration metadata is embedded in the data JSON because the staging schema has no additional_data column.
• support_tickets_comments.sql: imports 427 EGBIM posts into baron_support.support_tickets, creates post mappings, and imports 677 legacy comments into ticket_comments.
• support_ticket_secrets.sql: applies EGBIM is_secret or is_private to mapped baron_support.support_tickets.
• support_attachments.sql: inserts resolved post attachments and comment images into baron_support.attachments after support ticket/comment mappings exist.
• uploads_manifest.csv: audit list with source path, target storage key, checksum, and copy status.

The referenced files were copied to uploads/EGBIM_QA/. The container sees them under /app/uploads/EGBIM_QA/.

Required order

1. Apply the support schema/migration that creates migration_mappings, support_tickets, ticket_comments, and attachments.
2. Run support_tickets_comments.sql against baron_support. It creates 427 tickets, post mappings, and 677 comments.
3. Run userfeedback_feedbacks.sql against the ABC userfeedback database.
4. Run support_ticket_secrets.sql against baron_support.
5. Run support_attachments.sql against baron_support. It resolves the EGBIM workspace automatically and links post/comment files through the mappings.

The one missing source file is recorded in uploads_manifest.csv as MISSING; do not create a fake attachment row for it.