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.

Awaiting Matt’s approval

The finish line

Danubisoft has the same two campaigns and the same intended leads as ClientsFlow, both paused. Before capacity is freed, every current Danubisoft lead and its available campaign data is preserved in a separate Google Sheet. Nothing sends.

  1. Archive current Danubisoft data
  2. Prove the archive is complete
  3. Free enough Danubisoft lead slots
  4. Copy both ClientsFlow campaigns
  5. Verify both are paused and correct

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 their intended leads and campaign setup.

Success proof

  • Each source campaign is identified in ClientsFlow and matched to one Danubisoft destination.
  • Lead counts, unique emails, mapped fields, sequence content, and essential settings match the source.
  • Provider readback shows no partial import or unexplained reject.
Screenshot placeholder: source-to-destination campaign comparison

Must not

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

Paused, visible handoff

Matt can inspect the completed Danubisoft campaigns directly.

Success proof

  • Both destination campaigns visibly show Draft or Paused.
  • Fresh activity readback proves no outreach occurred.
  • The ChatGPT side-panel browser is left on the Danubisoft campaign interface.
Screenshot placeholder: both Danubisoft campaigns visible and paused

Must not

  • Do not launch, resume, schedule, or send either campaign.
  • Do not leave the browser on ClientsFlow, a login page, or a sending control.

Rules the future LUNA.MaX 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.

Waiting for approval. No execution agent has been launched and no Instantly or Google Sheet data has been changed by this contract.

Contract C01, revision 1. Parent acceptance owner: Matt in the current Codex task. After approval, one fresh LUNA.MaX agent receives this outcome contract through /goal, maintains the blue progress record, verifies every criterion, and returns one private final report.