Move two campaigns. Preserve everything.

Goal contract for copying the two approximately 150-lead ClientsFlow Instantly campaigns into the correct Danubisoft Instantly account, while safely archiving the leads currently occupying Danubisoft’s capacity.

Approved for execution

The finish line

Danubisoft has the same two campaigns and every intended lead from ClientsFlow in the proper matching campaign, with clean, natural copy, and both campaigns are running within 50 minutes of goal assignment. Before capacity is freed, every current Danubisoft lead and its available campaign data is preserved in a separate Google Sheet. The campaigns must not start until all archive, import, mapping, and copy checks pass.

  1. Archive current Danubisoft data
  2. Prove the archive is complete
  3. Free enough Danubisoft lead slots
  4. Copy both ClientsFlow campaigns
  5. Verify the imports and copy, then launch both

Deliverables and proof

Separate Google Sheet archive

All current Danubisoft leads and available campaign data are preserved outside Instantly.

Success proof

  • Fresh Instantly counts equal exported and Sheet counts.
  • Headers and lead identities reconcile without unexplained loss.
  • The final report links the separate Sheet and a private checksum receipt.
Screenshot placeholder: separate Google Sheet with archive totals

Must not

  • Do not remove any lead before the Sheet readback passes.
  • Do not overwrite an existing operational Sheet or change sharing.

Enough free Danubisoft slots

The archived current leads no longer consume the capacity needed for the two incoming campaigns.

Success proof

  • Provider readback proves the archived source set was removed.
  • Available capacity is sufficient for both source campaigns before either copy begins.
  • Unrelated campaigns and account settings remain unchanged.
Screenshot placeholder: capacity available for both campaign copies

Must not

  • Do not delete a broader workspace scope than the verified archive.
  • Do not buy or upgrade a plan.

Two matching campaign copies

The two ClientsFlow campaigns appear in Danubisoft with every intended lead in the proper matching campaign and the complete campaign setup.

Success proof

  • Each source campaign is identified in ClientsFlow and matched to exactly one Danubisoft destination.
  • For each campaign, source and destination lead counts and unique email sets reconcile exactly, mapped fields are correct, and no lead is assigned to the wrong campaign.
  • Sequence content, subject lines, sender setup, links, personalization, and essential settings match the intended source.
  • Provider readback shows no partial import, duplicate, unexplained reject, or cross-campaign mix-up.
Screenshot placeholder: source-to-destination campaign and lead reconciliation

Must not

  • Do not alter or delete the ClientsFlow source campaigns.
  • Do not silently substitute another lead list, sequence, or sender setup.

Verified launch and visible handoff

After every prerequisite passes, both Danubisoft campaigns are launched within 50 minutes of goal assignment and Matt can inspect them directly.

Success proof

  • A final human-readable copy review confirms the subjects and every sequence step are correct, natural, and free of awkward mistakes before launch.
  • Provider readback and timestamped evidence show both destination campaigns are Active or Running no later than 50 minutes after the goal assignment timestamp.
  • Fresh activity readback shows only the intended two campaigns were launched.
  • The ChatGPT side-panel browser is left on the Danubisoft campaign interface with both running campaigns visible.
Screenshot placeholder: both Danubisoft campaigns visible and running, with launch time

Must not

  • Do not launch either campaign before the archive, capacity, exact lead reconciliation, field mapping, sender setup, and copy review checks all pass.
  • Do not launch, resume, alter, or send from any unrelated campaign, and do not leave the browser on ClientsFlow or a login page.

Rules the Sol Medium agent must keep

Agent progress

After approval and launch, every sentence, link label, evidence note, and screenshot caption added by the agent must remain blue. The black contract above must not be weakened or rewritten.

Approved by Matt through browser annotations. Execution is assigned to a fresh Sol agent at Medium reasoning. No execution result is claimed here until the agent records provider and screenshot evidence.

Assignment recorded: 2026-09-21 15:13:10 CEST. Contract C01 revision 2 and both approved annotation requirements are loaded. Execution verification has begun.

2026-09-21 15:39 CEST · ARCHIVE VERIFIED: a separate native Google Sheet now holds 912 lead rows, 912 unique normalized emails, and all 60 exported provider columns. Fresh destination B readback also returned 912 unique emails and its normalized email-set SHA-256 exactly matched the private export. Destination A currently returns zero leads. The archive Sheet is Danubisoft Instantly pre-migration archive 2026-09-21.

2026-09-21 15:43 CEST · SOURCE RECONCILED: fresh ClientsFlow provider readback found 145 unique leads in A and 147 unique leads in B. Both source campaigns remain Draft and share the approved sequence hash. The matching Danubisoft drafts preserve the six previously approved Danubisoft sender accounts, weekday 09:00–16:30 schedule, daily limit 12, 13-minute minimum gap, 8-minute random wait, and reply, auto-reply, and company safety stops.

2026-09-21 15:45 CEST · COPY REVIEW READY: both destinations contain one identical subject and one identical sequence step. Representative personalization renders naturally. Definite wording corrections were prepared without changing the free-design offer or the sub-150,000 Ft implementation price. No lead deletion, import, launch, or send has occurred while the required action-time deletion and launch confirmations remain outstanding.

2026-09-21 15:48 CEST · ARCHIVED SET REMOVED: after Matt's explicit live-action confirmation, the exact 912-lead destination B set was deleted. Fresh provider UI readback shows destination A = 0 leads and destination B = 0 leads. Instantly's upload-capacity warning disappeared after a fresh campaign reload, confirming that the workspace capacity was released. The archive Sheet remains private and unchanged.

2026-09-21 16:01 CEST · LAUNCH GATE BLOCKED: the private CSV upload control rejected the workspace file, while Instantly's Google Sheets importer required the source Sheet to be publicly accessible. Making 292 prospect records public was not authorized and was not attempted. An authenticated private-session import route was also attempted but did not complete before the deadline. Both destination campaigns therefore remain Draft with zero leads. Copy edits were not saved and neither campaign was launched or sent.

2026-09-21 16:01:45 CEST · DEADLINE RESULT: BLOCKED. Required launch acceptance failed because A did not contain the reconciled 145-lead set, B did not contain the reconciled 147-lead set, and neither campaign was running at the hard cutoff. Safe recovery state: the complete 912-lead archive is verified, old leads are removed, both intended campaign drafts and approved sender/settings setup are preserved, and no prospect message was sent.

2026-09-21 after 16:01:45 CEST · EXECUTION WINDOW EXTENDED: Matt explicitly directed continued recovery and launch after the missed 50-minute SLA, while preserving the private archive, forbidding public Sheet exposure, and forbidding empty-campaign launch. The SLA miss remains part of the permanent record and is not reclassified as on-time completion.

2026-09-21 16:16 CEST · RECOVERED AND LAUNCHED LATE: authenticated private imports completed without changing either helper Sheet's access. Fresh provider reconciliation shows A = 145 unique leads with source hash 633fb5ad92fe65929839122a9f096350792a549a3030eb07e2b749fb0c47e44b and B = 147 unique leads with source hash 65f10e9f0dcaa3bbe3e74ee467718a83143522e0c574bfbb04d2534c02b57cfd. Both campaigns now use the proofread subject Elkészült a weboldalterv and corrected approved body, preserve all six Danubisoft senders, weekday 09:00–16:30 Belgrade schedule, daily limit 12, 13-minute gap, 8-minute random wait, and reply, auto-reply, and company safety stops. Provider status readback returned 1 for both campaigns, and the Danubisoft campaign list visibly shows both as Active. No unrelated campaign was changed.