Outreach → 11x

Catalog plan outline

General guidance from the Afterstack catalog for Outreach → 11x. Not Outreach or 11x vendor documentation.

Migration friendliness

Outreach 6/10 · 11x 4/10

Speed to live

Outreach 4/10 · 11x 6/10

Catalog migration difficulty

Outreach high · 11x medium

Data to export from Outreach

• pipeline and deal records
• sequences and cadences
• call and voice logs
• synced email and calendar links
• workflow rules
• saved reports
• installed marketplace apps
• AI assistant configuration
• records for the catalog use cases: outbound, sequences

How the catalogs differ

• Neither product is flagged for custom objects. Keep the object list short.
• 11x is not flagged for: pipeline and deal records, installed marketplace apps.
• Outreach is flagged with an open API, which is the export path to test.
• 11x is flagged with an open API for the load.
• Outreach is cataloged as a fit for: Enterprise SDR orgs.
• 11x is cataloged as a fit for: Teams that wanted an SDR workforce, not a sequencer UI.

Phases

1. Export

   Take Outreach as the source of truth for this pair. Export pipeline and deal records; sequences and cadences; call and voice logs; synced email and calendar links; workflow rules; saved reports; installed marketplace apps; AI assistant configuration; records for the catalog use cases: outbound, sequences. The default enterprise sales-engagement platform — sequences, calls, and a lot of admin.

2. Map

   Load into 11x only after the field map is written down. Digital workers for outbound — AI-native substitute for an SDR pod. Neither product is flagged for custom objects. Keep the object list short.

3. Prove a sample

   11x scores 6/10 on speed to live and 4/10 on migration friendliness. Run one sample load and one report the team already uses in Outreach before a full cutover.

4. Cut over

   Outreach scores 6/10 on migration friendliness and is marked high difficulty in the catalog. Keep Outreach readable until the team is working in 11x. Outreach is the procurement-safe sales engagement suite: sequences, dialer, analytics, and a platform that grew around SDR teams. AI features have been added onto a sequencer that was not designed as an autonomous seller. This is the incumbent many teams are trying to leave.

Outreach to 11x: what the vendor docs actually cover

Linked sentences come from vendor documentation opened for this page. Everything else is general guidance, not Outreach or 11x vendor documentation. This section does not move data and does not change the catalog outline above.

What to export from Outreach

Outreach's public REST reference, opened 2026-10-17, is the export side. Prospects are GET /api/v2/prospects, and sequence membership is a separate resource: GET /api/v2/sequenceStates. A sequence state points at a prospect, a sequence, a mailbox, and the current step. The prospects page says activeSequenceStates are the non-finished memberships, including active, paused, failed, bounced, pending, and disabled. Opportunities on a prospect require the Opportunities SKU. Server-to-server tokens, documented on the S2S access page, cover a narrower scope list than interactive OAuth. That list includes prospects, sequences, sequence states, mailings as read, accounts, calls, tasks, templates as read, and users as read. The common-patterns guide shows how a sequence is created as type interval or date, how a step is auto_email, call, manual_email, or task, and how a sequence state is the act of placing a prospect into a sequence on a mailbox. None of that is a file format 11x accepts. Outreach's pricing page the same day names Amplify Essentials, Core, Plus, and Pro and says reach out for custom pricing. The FAQ describes seat access plus consumption credits. Essentials is written as 10K credits and Core as 25K credits. No dollar amount is on the page. The catalog's empty starting price and custom model match. A trial length is not written; the calls to action are request pricing and request a demo, so the catalog trial flag is unverified.

• Outreach prospects collection — checked 2026-10-17
• Outreach common API patterns — checked 2026-10-17
• Outreach pricing — checked 2026-10-17

How 11x imports

11x prices Alice and Julian separately. The pricing overview opened 2026-10-17 says Alice Growth is from 3,750 dollars a month, billed annually, with up to 5 end users and 2,000 new prospects a month. Pro and Enterprise are custom. Alice is priced per prospect, not per send. API access, custom integrations, and SSO sit on the Alice Enterprise column, not on Growth. The page says there is no published self-serve free trial. The entry is a demo. Rechecked 2026-10-19, the catalog stores Alice Growth at $3,750 a month on a flat model and hasFreeTrial false, which matches that overview. Julian voice Growth is from 5,333 dollars a month and chat Growth from 2,417, which matters only if the buyer is also purchasing inbound. The webhooks page says one API spans Alice and Julian, that you push prospect attributes in and pull outcomes out, and that the endpoint reference is not published yet. It tells you to email support@11x.ai. Native connectors it names are Salesforce, HubSpot, and Pipedrive. Outreach is not in that table. Julian's calling API, a different host, documents POST /agents/{agentId}/schedule/sequences for up to 1,000 contacts, which it calls the API equivalent of CSV import. A 202 means the contacts were queued, not that sequences exist yet. There is no public batch-status endpoint. Phone duplicates collide after normalization, and a sequence already in progress or started within 30 days is rejected unless allowDuplicates is true. That Julian contract is a calling enroll. It is not an importer for Outreach interval sequences, rulesets, or mailbox assignments. Sequences do not move as sequences. People can be re-enrolled into an 11x play. The sequencer floor can stay if humans still need it.

• 11x pricing overview — checked 2026-10-17
• 11x webhooks and API — checked 2026-10-17
• Julian enroll multiple contacts — checked 2026-10-17

Object and field mapping

• An Outreach prospect is the person. An 11x contact on the Julian bulk call is a phone number plus whatever custom variables the agent requires. The docs tell you to call List agent input variables. They do not list Outreach fields.
• An Outreach sequence state is one person inside one sequence on one mailbox. 11x sequences are plays the worker runs. The webhooks page does not say an Outreach step type survives.
• auto_email, call, manual_email, and task are Outreach step types in the common-patterns guide. Alice's pricing page says touchpoints do not change the prospect price. That is a billing fact, not a field map.
• Mailings are readable with an S2S token and are history. Nothing on the 11x pages says historical sends import.
• Opportunities need an Outreach SKU. 11x writes outcomes back to a CRM it names. Outreach itself is not that CRM in the connector table.
• Alice API access is an Enterprise line. Buying Growth and expecting the unpublished endpoint list is not what the pricing table says.
• Julian's Idempotency-Key and 600 requests a minute are calling-API limits. They are not Outreach rate limits.

What will not carry over

• Outreach sequence structure, rulesets, and mailbox assignment.
• A named Outreach connector. The 11x table lists three CRMs and not Outreach.
• The unpublished Alice endpoint list. The webhooks page says it is not public.
• Historical mailings and call recordings, which neither 11x page accepts as an import file.
• A self-serve 11x trial. The pricing overview says there isn't one.
• A dollar price for Outreach Amplify. The page is a quote.
• Julian as if it were Alice. Calling enroll is a different product and a different host.

Cutover checklist

1. Pull prospects with the REST collection, then sequence states, if you need to know who is mid-cadence. Do not treat a prospect record as the cadence.
2. Use an S2S token only for scopes on that page. Interactive OAuth is a different install.
3. Decide whether Outreach keeps sending during overlap. 11x will not inherit the pause state.
4. If the motion is Alice outbound, ask for the unpublished endpoint list. Growth does not include Alice API on the pricing table.
5. If the motion is Julian calling, enroll at most 1,000 contacts a request, send Idempotency-Key, and read rejected[] rather than assuming the whole file landed.
6. Normalize phones before enroll. The Julian page says formatting variants collide, and a 30-day in-progress sequence blocks a repeat.
7. Keep a human sequencer if managers still need Outreach tasks. This pair does not document a dialer replacement.
8. Quote Alice from 3,750 dollars a month on annual Growth. The catalog now stores that figure on a flat model.

Common pitfalls

• Pasting an Outreach sequence POST body into 11x. The step types are Outreach's.
• Treating Julian's CSV-equivalent enroll as an Alice migration. The hosts and the workers differ.
• Expecting Salesforce-style CRM sync to cover Outreach because both are sales tools. The connector table does not say that.
• Reading a trial into 11x. The pricing overview denies a self-serve trial, and the catalog trial flag is false.
• Ignoring allowDuplicates and then debugging missing rows. Default behavior drops the second phone.

Related catalog pages

• Best AI-native Outreach alternatives (2026) — Which tool, compared
• What should replace Outreach? — Switch narrative
• 11x product page — Digital workers for outbound — AI-native substitute for an SDR pod.
• 11x vs Outreach — Head-to-head already in the catalog
• Sales engagement category — Catalog hub for this category