15 - Migration Status, Call Notes & Open Questions

The living status page for the CARR -> Barry-Wehmiller / Azure migration. Captures the latest working session, the confirmed Azure target, and the open questions in flight, so the whole team (BC + CARR + BW) is working from one current picture. Updated 2026-07-21.
Triggers: "migration status", "where are we", "db access", "next steps", "open questions", "azure sql credentials".

Latest working session - 2026-07-21

Working call on the path forward for migrating the CARR Intel Hub to Barry-Wehmiller's Azure environment. Not recorded - these are the captured notes.

• Attendees: Brian Elbert (BioCreative), Saeed Allahbaksh (Barry-Wehmiller), Colby Bishop (CARR, Product Manager).
• Frame: good alignment on the path forward; the remaining items are access + a handful of architecture decisions (below), not disagreements on direction.
• Post-call: the BioCreative Agent-Building Stack guide was shared with Colby, Saeed, and Blake Feinstein (BW Forsyth) so the BW/CARR side can see how the agents are built. It is on this site - see 16_agent_building_stack.md and the per-agent mapping in 11_carr_agent_fleet.md.

Confirmed Azure SQL target (the destination)

Barry-Wehmiller has stood up the Azure SQL database that the CARR platform migrates into. This is the real target for the Postgres -> Azure SQL conversion in 07_azure_sql_conversion.md.

Item	Value
Server	cbsuse-sql01.database.windows.net
Database	siplatform
Client tool	SQL Server Management Studio (SSMS)
Auth	MFA + Barry-Wehmiller credentials
Brian's login	Brian.Elbert@carrbiosystems.com
Provisioned by	Landon (BW), with setup instructions handed to BioCreative

Access status: pending credentials. The database + Brian's access were set up, but the login above needs its Barry-Wehmiller email credentials issued before BioCreative can connect. Colby has asked Chad Evans (BW-NA) to help issue them. The Supabase -> Azure SQL migration is prepped and ready to begin the moment those credentials land - this is the current gating item.

Open questions in flight

From the current working thread. BC's position on each is noted; final calls sit with BW/CARR.

1. DB credentials (gating). Issue the BW/CARR email credentials for Brian.Elbert@carrbiosystems.com so BioCreative can reach siplatform. Owner: Chad Evans (BW) with Colby. Blocks everything downstream.
2. Data-warehouse layer - now or later? Do we add a warehouse layer now, or treat it as future-state once the platform is pulling from multiple source systems (CRM, HubSpot, XA)? BC position: future-state. Land the single-source Azure SQL migration first; add a warehouse only when multi-source consolidation is real. See 07.
3. Frontend + compute topology. Dashboard on Azure Static Web Apps talking to a backend on Azure Container Apps; BioCreative can author the Dockerfile and push the image to the Container Registry. Open: does the Container Apps + Registry deployment need a separate resource group / permissions from the one created for the DB? BC position: confirm the RG/permission model with BW cloud ops before we build the image. See 03_compute_frontend.md.
4. Agents / LLM runtime. Microsoft Foundry looks like the right home for the agents that scrape + curate data, but no Barry-Wehmiller user with Foundry access has been found yet. Open: is there anyone at BW who has used Foundry, and can CARR explore it with BioCreative - or do we fall back to recreating the agents via Claude Cowork? BC position: Foundry is the target (see 02_ai_foundry_agents.md + the fleet in 11); Cowork is a viable interim only if Foundry access stalls. The agent-build method is documented in 16_agent_building_stack.md.

Immediate next steps

#	Step	Owner	Blocked by
1	Issue BW email credentials for Brian.Elbert@carrbiosystems.com	Chad Evans (BW) + Colby	-
2	Connect via SSMS + begin Supabase -> Azure SQL conversion (07)	BioCreative	Step 1
3	Confirm resource group / permissions for Container Apps + Registry	BW cloud ops + Colby	-
4	Author the Dockerfile + push backend image to the Container Registry	BioCreative	Step 3
5	Locate a BW Foundry user / confirm access path for the agent fleet	BW + Colby	-
6	Decide data-warehouse timing (now vs future-state)	BW + CARR	-

Cross-references

• Postgres -> Azure SQL conversion (targets siplatform): 07_azure_sql_conversion.md
• Compute + frontend hosting (Static Web Apps + Container Apps): 03_compute_frontend.md
• Foundry + the agent runtime: 02_ai_foundry_agents.md
• The planned CARR agent fleet: 11_carr_agent_fleet.md
• How we build agents (the shared method): 16_agent_building_stack.md
• Whole-system map: ../CARR_FULL_SYSTEM_MIGRATION_MAP.md