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.

Contract C01, revision 2. Parent acceptance owner: Matt in the current Codex task. One fresh Sol agent at Medium reasoning receives this outcome contract through /goal, maintains the blue progress record, verifies every criterion, launches only after all prerequisites pass, and returns one private final report.