Most migrations involve one tool. This one involves up to six.
Salesforge sells outbound as separate products: Salesforge for sequencing, Agent Frank as the AI SDR, Leadsforge for lead data, Primeforge for Google and Microsoft mailboxes, Infraforge or Mailforge for private infrastructure, Warmforge for deliverability and Primebox for the inbox.
Each has its own login, its own billing and its own export. Which means the first task is not planning a migration, it is working out what you are actually subscribed to.
Step one: inventory
Open your billing and list every Forge product with its monthly cost and renewal date. Teams are routinely surprised by two things: how many there are, and that the renewal dates differ, which matters when you plan a cancellation.
For each one, note what it holds that you would miss:
| Product | What it holds | Exports as |
|---|---|---|
| Salesforge | Sequences, campaign analytics | CSV for analytics; sequences do not export |
| Agent Frank | AI configuration, reply handling rules | No export, document the settings |
| Leadsforge | Lead lists, enrichment | CSV |
| Primeforge | Google/Microsoft mailboxes | Account list; mailboxes are provisioned |
| Infraforge / Mailforge | Private infrastructure, domains | Account list; check domain ownership |
| Warmforge | Warmup history and scores | Nothing portable |
| Primebox | Reply threads | No export |
The question that decides your timeline
Who owns the domains and mailboxes?
If you bought mailboxes through Primeforge, Infraforge or Mailforge, check the registrar on your sending domains. If they sit in a Forge account rather than yours, cancelling means losing warmed infrastructure and starting a new estate, three to four weeks of warmup before you are back at volume.
If the domains are in your own registrar account and the mailboxes run over standard SMTP and IMAP, you reconnect them elsewhere and keep everything.
This single answer is the difference between a 30-day migration and a 60-day one, so establish it before you plan anything. Who owns your cold email domains covers how to handle it if the answer is unwelcome.
Document Agent Frank before you cancel
If you run Agent Frank, its configuration is genuinely valuable and completely unportable. Before cancelling, write down:
- Autonomy level per campaign, and what it was allowed to send unreviewed
- Reply categories it handled autonomously versus escalated
- Escalation rules, which accounts, which topics, which sentiment
- The offer and positioning you trained it on
- Any guardrails on claims, pricing or commitments
That document is your configuration spec for whatever replaces it. Rebuilding an AI reply agent without it means rediscovering by trial which reply types you trust it with, and the trial happens on real prospects.
What consolidation actually changes
Worth being specific, because “one platform instead of six” is a slogan until you say what it means operationally.
One suppression list. In a split stack, unsubscribes live wherever the send happened. Consolidating means a single workspace-level suppression list that every channel honours, which is the single most common compliance gap in multi-product setups.
One place a lead lives. Today the lead record is in Leadsforge, the campaign in Salesforge, the reply in Primebox and the mailbox in Primeforge. Reconciling those is somebody’s weekly job.
One bill, one renewal date. Minor, until you try to time a cancellation across six products with different cycles.
Deliverability has one owner. When placement drops in a split stack, the infrastructure product, the warmup product and the sequencer can each credibly point at another. That argument costs a fortnight.
The honest counterpoint: if you genuinely only use two of the six, the unbundled model was serving you fine and consolidation buys less than it appears. The unbundled stack piece makes both sides of that case.
The plan
Week 1, export from every product
Work through the list above, product by product. Unsubscribes first, from wherever sends originated, and check each product separately, because a suppression in Salesforge may not exist in Primebox.
Then leads from Leadsforge, analytics from Salesforge, account lists from the infrastructure product, and your Agent Frank configuration document.
Copy sequences as text. Note which steps Agent Frank was handling versus which were fixed.
Week 2, consolidate suppressions, then set up
Merge every suppression source into one list. This takes longer than expected in a split stack and it is the step that must not be rushed.
Create the workspace, load the merged suppression list, recreate custom fields, import leads, bulk-connect mailboxes.
Everything keeps running on the Forge products meanwhile. You are adding a second route, not switching.
Week 3, rebuild one campaign with the AI layer
Rebuild your best campaign. Configure the reply agent from your Agent Frank document, but start in draft-and-approve rather than matching its old autonomy level straight away, the models differ and so will the output.
Run at 20% of volume. Compare reply rates on comparable segments while both are live.
Week 4, shift, then cancel in the right order
Ramp 30% every few days.
Cancel in this order: the AI layer first, then sequencing, then data, then the inbox, and infrastructure last, because if anything goes wrong you want the mailboxes still working while you fix it. Watch the differing renewal dates so you are not paying for a product you stopped using three weeks ago.
The cost comparison
Using publicly listed pricing verified on 19 October 2026: Salesforge Pro is $40 a month and Growth $80. Agent Frank is $499 billed quarterly, with an email infrastructure add-on at $416 covering up to 1,000 active contacts. Leadsforge starts at $49. Infrastructure through Primeforge, Infraforge or Mailforge shows as $86 to $123 a month for 25 mailboxes and 8 domains. A setup with the AI layer and data passes $1,000 a month.
Outboundry’s Agency plan is $399 with 20 LinkedIn seats, whitelabel and workspaces, unlimited email accounts, and infrastructure in the same product from $0.80 to $2.50 a mailbox. AI actions are 1 credit each, with credits from $0.0083.
Verify both against current pricing pages before deciding, this part of the market moves, and the Forge pricing in particular is spread across six sites.
One thing worth checking carefully: LinkedIn social actions. Salesforge meters profile views, connection requests and messages against a shared allowance (300 a month on Pro, 1,000 on Growth) and Pro allows only one LinkedIn sender. If LinkedIn is a real channel for you, model that before anything else.
The short version
Inventory the Forge products you actually pay for before anything else, the total is usually higher than the Salesforge line suggests, and the renewal dates differ.
Establish who owns the domains. That sets your timeline.
Document Agent Frank’s configuration, because it is the most valuable unportable thing you have. Merge suppressions from every product into one list before importing a single lead. And cancel infrastructure last, so the mailboxes still work if something needs fixing.
Next: six products or one platform, priced, or the universal migration checklist.
Frequently asked questions
How many products make up the Salesforge stack?
Up to six or seven: Salesforge for sequencing, Agent Frank for AI, Leadsforge for data, Primeforge for mailboxes, Infraforge or Mailforge for infrastructure, Warmforge for deliverability and Primebox for the inbox, each billed separately.
Can I export my Agent Frank configuration?
No. Autonomy settings, escalation rules and the positioning it was trained on have to be documented by hand before you cancel.
Will I lose my mailboxes leaving Salesforge?
Only if the domains are registered to a Forge account rather than yours. Check your registrar first, mailboxes running over standard SMTP and IMAP on domains you own reconnect elsewhere intact.
What order should I cancel the Forge products in?
AI layer first, then sequencing, data and inbox, with infrastructure last so your mailboxes keep working if something needs fixing mid-migration.
