How to migrate from Apollo to 11x in 2026: step-by-step playbook
Most revenue teams complete the Apollo-to-11x migration in 4–6 weeks when they follow a parallel-pilot approach, exporting 8–12 core artifacts and warming new sending domains before cutover.
Major takeaways
How long does it take to migrate from Apollo to 11x? 4–6 weeks for most teams, including a 2-week parallel pilot. Running both platforms side-by-side during weeks 3–4 cuts deliverability risk and preserves reply rates during the transition.
What can I export from Apollo? Contacts, lead lists, sequence templates, sender domains, SPF/DKIM/DMARC records, reply history, and integration maps export cleanly. Custom AI personalization prompts and trigger-based workflows require manual rebuild.
Will my deliverability drop during migration? It can drop 10–15% temporarily if you skip domain warm-up. A 14-day staggered cutover with SPF/DKIM/DMARC authentication and gradual volume ramp keeps deliverability stable.
Why teams migrate from Apollo
Apollo reportedly serves over 10,000 customers and provides real value for teams that need a sales intelligence and engagement platform with a large contact database. Teams that migrate typically do so for one of five reasons, not because Apollo failed to deliver on its core promise.
Renewal pricing increases beyond budget
Apollo's pricing reportedly increased 20–30% at renewal for some customers in 2024–2025, based on third-party reports on Reddit and G2. Teams with 10+ seats often face annual contract values above $50,000, which pushes the platform outside budget for mid-market teams. Procurement teams note that Apollo's auto-renewal windows (typically 60–90 days) require early notice to avoid unintended contract extensions.
Capability gap (typically inbound voice or multilingual)
Apollo focuses on outbound email and LinkedIn. Teams that need inbound phone qualification or multilingual outbound (beyond English, Spanish, French, and German) reportedly find gaps.
11x's Julian handles inbound voice with sub-60-second speed-to-lead. Alice operates in 105+ languages, which covers ICPs in APAC, LATAM, and EMEA that Apollo's platform does not natively support.
Deliverability or sender-reputation issues
Multiple G2 reviewers cite deliverability challenges when sending volume exceeds 500 emails per day per sender. Apollo's shared IP pools reportedly expose users to reputation damage from other customers' sending practices. Teams that migrate to 11x often do so to isolate sender reputation and control domain authentication end-to-end.
Slow time-to-first-meeting in production
Apollo sequences reportedly take 14–21 days from first touch to booked meeting for cold outbound. Teams that need faster conversion cycles (SaaS trials, event registrations, demo requests) find that Apollo's step-delay structure and manual reply-handling slow the motion.
11x's Alice responds to inbound replies within minutes and books meetings without human intervention, which cuts time-to-first-meeting to 3–7 days in production.
Roadmap pace and AI-native architecture
Apollo's AI features (personalization, reply detection, intent signals) are add-ons to a platform built for manual workflows. Teams that want AI-first architecture—where the agent writes, sends, qualifies, and books without human prompting—report that Apollo's feature set lags behind AI-native platforms.
11x ships Alice and Julian as autonomous agents, not assistants. This changes the operational model from "rep + tool" to "agent + oversight."
Pre-migration checklist
Migration planning takes 1–2 days and prevents the most common failure modes: missing the auto-renewal window, losing sequence templates, and breaking CRM sync during cutover.
What to inventory before you start
RevOps should inventory the following artifacts inside Apollo before exporting anything:
Active and paused sequences. Count the total number of sequences, note which are live, and pull baseline metrics (send volume, reply rate, meetings booked) for the last 30 days.
Sender accounts and sending domains. List every connected mailbox, the sending domain for each, and the current warm-up status. Note whether domains are shared across reps or dedicated per sender.
Authentication records. Document SPF, DKIM, DMARC, and BIMI records for every sending domain. These must be replicated in 11x to preserve deliverability.
Lead lists and saved searches. Export the filters and criteria for each saved search. Apollo's list-building logic may not map 1:1 to 11x's segmentation, so document the intent behind each list.
Custom fields, snippets, and merge tags. Apollo allows custom fields at the contact and account level. Build a mapping table in a spreadsheet that shows Apollo field names, data types, and the corresponding 11x field (or note where a new field must be created).
Reporting dashboards and KPIs. Screenshot or export the dashboards your team relies on. You'll rebuild these in 11x during week 2.
Integration map. List every connected system: CRM (Salesforce, HubSpot, Pipedrive), calendar (Google, Outlook), conversation intelligence (Gong, Chorus), dialer (Aircall, Dialpad). Note which integrations push data to Apollo and which pull data from it.
Active enrichment and data-source subscriptions. If you use Apollo's enrichment credits or third-party data sources, note the monthly spend and the fields being enriched. 11x includes a native 400M+ verified contact database, which may replace some of these subscriptions.
Open replies and meetings booked in the last 30 days. Pull a CSV of all replies and meetings from the last 30 days. This baseline will be used to compare 11x performance in weeks 4–6.
This inventory typically takes 4–8 hours for a team with 5–10 active sequences and 3–5 connected integrations. RevOps owns this step.
Stakeholders and approvals
Migration requires sign-off from five stakeholders, each with a specific approval gate:
RevOps lead approves the migration plan, timeline, and cutover date. This person owns the project end-to-end.
Sales leader approves the parallel-pilot design (which reps, which sequences, which ICP) and the cutover window. Sales will resist migration during active quota periods, so plan for early-quarter or planning weeks.
Marketing Ops approves changes to lead routing, form integrations, and inbound-to-outbound handoff logic if Julian is being adopted for inbound voice.
IT/Security approves domain authentication changes (SPF, DKIM, DMARC), new vendor onboarding (11x's SOC-2 Type II compliance), and data-export procedures.
Procurement reviews the Apollo contract for early-termination terms, auto-renewal deadlines, and data-deletion requirements. Legal should review the contract in parallel to confirm that exporting contact data and sequence templates does not violate Apollo's terms of service.
Most teams complete stakeholder alignment in 1–2 meetings during week 1.
Step 1: export your data from Apollo
Apollo provides native CSV exports and API access for most artifacts. The export process takes 2–4 hours for a team with 10,000+ contacts and 10+ sequences.
Contacts and lead lists
Apollo's native export (Settings → Data Management → Export Contacts) produces a CSV with all contact fields, including custom fields. The export includes contact name, email, phone, company, title, and any enrichment data (technographics, intent signals, funding stage).
Custom fields may not map 1:1 to 11x's schema. Build a mapping table in a spreadsheet before importing.
For example, if Apollo has a custom field called "ICP_Score" (integer, 1–10), decide whether this maps to a custom field in 11x or to a tag/segment. Document the mapping logic so the import step in week 2 is deterministic.
Lead lists (saved searches) export as static CSVs. The filters and criteria do not export automatically. Document the logic for each list in a separate spreadsheet so you can rebuild the segmentation in 11x.
Sequence templates
Apollo does not provide a bulk export for sequences. Each sequence must be copied manually, step by step. For each sequence, document:
Step number and delay. Example: Step 1 (Day 0), Step 2 (Day 3), Step 3 (Day 7).
Channel. Email, LinkedIn connection request, LinkedIn message, or phone call.
Subject line (for email steps).
Body content with merge tags intact. Apollo uses {{first_name}}, {{company}}, {{title}} syntax. 11x uses similar syntax, but verify the exact token names during import.
Personalization logic. If the sequence uses conditional content (e.g., different messaging for VP-level vs. Director-level contacts), note the logic.
A/B test variants. If the sequence has A/B tests on subject lines or body content, export all variants.
Most teams use a spreadsheet or Google Doc to capture this data. A 7-step sequence takes 15–20 minutes to document. Teams with 10+ sequences should allocate 3–4 hours for this step.
Sender accounts and authentication
List every connected mailbox in Apollo (Settings → Email Accounts). For each sender, document:
Email address.
Sending domain (e.g., @company.com or @outbound.company.com).
Current daily send volume (Apollo's dashboard shows this under Email Health).
Warm-up status. If the domain is fully warmed (30+ days, 200+ emails/day), note this. If it's still warming, note the current volume.
SPF record. Check your DNS provider (Cloudflare, Route 53, GoDaddy) and copy the SPF record for the sending domain.
DKIM key. Apollo generates a DKIM key for each connected domain. Copy the public key from Apollo's settings and the corresponding DNS record.
DMARC policy. Copy the DMARC record (_dmarc.yourdomain.com) from DNS. Note the policy (none, quarantine, reject) and the reporting email.
BIMI record (if configured). BIMI is optional but improves inbox placement for some ESPs.
This data is critical for preserving deliverability during cutover. If you skip this step, your reply rate will drop 15–25% in week 1 of the migration.
Reply and meeting history
Pull a CSV of all replies and meetings booked in the last 30 days. Apollo's reporting dashboard (Analytics → Sequences) allows export of reply data, including reply rate, positive reply rate, and meetings booked per sequence.
This baseline will be used to compare 11x performance in weeks 4–6. Most teams see parity at week 2 and a 10–20% uplift in reply rate by week 6, based on third-party reports from G2 and TrustRadius.
Step 2: set up 11x in parallel
11x setup takes 3–5 days, including domain authentication and CRM sync. Do not disconnect Apollo during this step. Both platforms run in parallel during weeks 2–4.
Provision Alice and Julian
Alice is 11x's AI SDR for outbound (email, LinkedIn, multi-channel). Julian is 11x's AI phone agent for inbound qualification and routing. Most teams start with Alice and add Julian once outbound is stable.
Provisioning takes 1–2 hours. You'll connect your CRM, authenticate sending domains, and configure Alice's ICP and messaging framework. 11x's onboarding team provides a dedicated CS resource for this step, which is included in the contract.
Connect your CRM and calendar
11x integrates natively with Salesforce, HubSpot, and Pipedrive. Calendar sync works via Google Workspace or Microsoft 365. The CRM connection is the highest-risk step for data fidelity.
Review field-mapping carefully. Apollo's custom fields (e.g., ICP_Score, Intent_Signal, Last_Touchpoint) must map to corresponding fields in your CRM or to new custom fields in 11x. Use the mapping table built in Step 1 to guide this process.
Most teams discover 2–3 fields that don't map cleanly. Document these as "manual rebuild" items and allocate 2–4 hours in week 3 to recreate the logic in 11x.
Calendar sync is straightforward. 11x pulls availability from Google or Outlook and books meetings directly into the rep's calendar. No manual intervention required.
Add and authenticate sending domains
Add the sending domains documented in Step 1 to 11x (Settings → Sending Domains). For each domain, configure:
SPF record. Add 11x's SPF include to your existing SPF record. Most domains already have an SPF record for Google Workspace, Microsoft 365, or another ESP. The combined record must stay under the 10-lookup limit to avoid SPF failures.
DKIM key. 11x generates a new DKIM key for each domain. Add the public key to your DNS provider as a TXT record.
DMARC policy. If your DMARC policy is set to p=reject, consider softening it to p=quarantine during the migration to avoid false positives. Revert to p=reject after 2–3 weeks of stable sending.
BIMI record (optional). If you have a BIMI record configured for Apollo, replicate it in 11x.
After authentication, start the 14-day domain warm-up. 11x's warm-up engine gradually increases send volume from 50 emails/day to 200+ emails/day over 14 days.
Do not skip this step. Skipping warm-up is the single biggest cause of deliverability drops during migration.
Import contacts and sequence templates
Use the mapping spreadsheet built in Step 1 to import contacts. 11x's import tool (Settings → Contacts → Import CSV) validates field types and flags errors before committing the import.
Validate a sample of 200 contacts manually before bulk import. Check that custom fields populated correctly, that tags/segments match the Apollo lists, and that phone numbers and email addresses are formatted correctly.
Sequence templates are rebuilt inside 11x's sequence editor. Copy the step-by-step content from the spreadsheet created in Step 1. 11x's merge-tag syntax is similar to Apollo's, but verify that {{first_name}}, {{company}}, and {{title}} tokens work as expected.
Most teams rebuild 1–2 sequences during week 2 and validate them in the parallel pilot (Step 3) before migrating the full sequence library.
Step 3: run a 2-week parallel pilot
The parallel pilot is the lowest-risk path to migration. It allows you to validate 11x performance against the Apollo baseline before committing to full cutover.
Split traffic 80/20
Keep 80% of outbound volume on Apollo and route 20% through 11x. The 20% should be a single rep, a single ICP, or a single geography—something small enough to monitor closely but large enough to generate statistically significant data.
Run the pilot for 2 weeks (10 business days). The primary metrics are:
Reply rate. Target parity with Apollo's baseline (typically 2–5% for cold outbound).
Positive reply rate. Replies that express interest, ask a question, or request a meeting.
Meetings booked. The ultimate conversion metric.
Reply-to-meeting conversion. The percentage of positive replies that convert to booked meetings.
Most teams see parity at week 2. Meaningful upside (10–20% higher reply rate, 15–25% faster time-to-meeting) typically shows up at weeks 4–6, based on third-party reports from G2 and TrustRadius.
Validate inbound voice (if applicable)
If you're adopting Julian for inbound speed-to-lead, configure call routing during week 2 and run a 50-call sample during the pilot. The primary metrics are:
Latency. Time from form submission to first call attempt. 11x targets sub-60-second latency.
Qualification accuracy. Percentage of calls that correctly identify ICP fit (budget, authority, need, timeline).
Routing accuracy. Percentage of qualified calls that route to the correct rep or team.
Julian's qualification logic is configured during onboarding. You'll define the ICP criteria (company size, industry, title, budget) and the routing rules (round-robin, territory-based, or account-based).
Most teams complete Julian validation in 3–5 days. If latency or qualification accuracy is below target, 11x's CS team adjusts the configuration before full rollout.
Compare to baseline
Use the baseline pulled in Step 1 (reply rate, meetings booked, time-to-meeting) to compare 11x performance. The comparison should be apples-to-apples: same ICP, same messaging framework, same send volume.
If 11x underperforms Apollo at week 2, the most common causes are:
Domain warm-up incomplete. If you started sending before the 14-day warm-up finished, deliverability will be 10–15% lower. Pause sending and complete the warm-up.
Messaging mismatch. If the sequence templates were copied verbatim from Apollo without adjusting for 11x's tone or personalization engine, reply rates may drop. Rewrite 1–2 sequences with 11x's CS team and retest.
CRM field-mapping error. If custom fields didn't map correctly, personalization tokens may be blank or incorrect. Fix the mapping and re-import the affected contacts.
If 11x matches or exceeds Apollo's baseline at week 2, proceed to Step 4 (cutover).
Step 4: cutover
Cutover takes 1–2 weeks and should be sequenced one sequence at a time. Avoid a big-bang cutover. Big-bang migrations almost always cause a 2–3 week reply-rate dip because reps lose familiarity with the new platform and sequences don't perform as expected under load.
Migrate sequence by sequence
Pause new launches in Apollo during weeks 4–5. Migrate sequences one at a time, starting with the highest-performing sequence from the pilot.
For each sequence:
- Rebuild the sequence in 11x (if not already done in Step 2).
- Import the contact list for that sequence.
- Launch the sequence in 11x.
- Pause the corresponding sequence in Apollo.
- Monitor reply rate and meetings booked for 3–5 days.
- If performance matches the baseline, proceed to the next sequence.
Most teams migrate 2–3 sequences per week. A team with 10 sequences completes cutover in 3–4 weeks.
Repoint sending domains
If you're moving sending domains entirely (e.g., from @outbound-apollo.company.com to @outbound.company.com), update SPF, DKIM, and DMARC records to point to 11x instead of Apollo.
Most teams keep their primary sending domain and add a secondary domain for 11x. This allows a gradual cutover without breaking existing Apollo sequences.
If you're consolidating domains, expect a 5–10% deliverability dip in week 1 as ESPs (Gmail, Outlook, Yahoo) learn the new sending pattern. The dip typically resolves within 7–10 days.
Disconnect Apollo integrations
Once all sequences are migrated, disconnect Apollo's integrations with your CRM, calendar, and other systems. Confirm with RevOps that no downstream automation (Zapier workflows, Salesforce flows, HubSpot workflows) depends on Apollo data.
Most teams discover 1–2 hidden dependencies during this step. Document them and rebuild the logic in 11x or directly in the CRM.
Archive Apollo reply history
Per legal and data-retention policy, archive Apollo's reply history before canceling the contract. Most teams export replies as a CSV and store them in Google Drive, Dropbox, or an internal data warehouse.
Some teams keep a 6–12 month read-only archive of Apollo for historical reporting. This is optional but recommended if your sales team relies on historical reply data for territory planning or quota setting.
Step 5: cancel Apollo cleanly
Contract cancellation takes 2–4 weeks, depending on Apollo's offboarding process and your legal team's data-deletion requirements.
Review contract early-termination terms
Apollo's contracts reportedly include auto-renewal clauses with 60–90 day notice windows, based on third-party reports on Reddit and G2. Surface this in week 1 of the migration so you don't miss the notice deadline.
If you're inside the auto-renewal window, you may be locked into another year. Some teams negotiate an early-termination fee (typically 25–50% of the remaining contract value) to exit early. Procurement should handle this negotiation.
Document the offboarding request
Email your Apollo CSM with a formal offboarding request. Include:
Cancellation date. The last day of active use.
Data-deletion request. Under GDPR (for EU contacts) and CCPA (for California contacts), you have the right to request deletion of your data from Apollo's systems. Include this in the offboarding email.
Sub-processor offboarding. If Apollo uses sub-processors (e.g., AWS, Google Cloud, third-party enrichment vendors), request confirmation that your data has been deleted from those systems as well.
Most teams receive confirmation within 7–14 days. If Apollo does not respond, escalate to your legal team.
Confirm data deletion and sub-processor offboarding
Get written confirmation that your data has been deleted from Apollo's systems and any sub-processors. This confirmation is required for GDPR and CCPA compliance.
If Apollo does not provide written confirmation, your legal team may need to send a formal data-deletion request under GDPR Article 17 (right to erasure) or CCPA Section 1798.105.
Update procurement records
Remove Apollo from your active vendor list and update the SaaS spend dashboard. If you're using a procurement platform (Vendr, Vertice, Tropic), mark Apollo as "canceled" and update the contract end date.
Most teams also update their security and compliance documentation (vendor risk assessments, SOC-2 audits, data-processing agreements) to reflect that Apollo is no longer a sub-processor.
Migration timeline at a glance
| Week | Owner | Key activities |
|---|---|---|
| 1 | RevOps | Inventory Apollo artifacts, export contacts and sequences, align stakeholders, review contract terms |
| 2 | RevOps + IT | Provision 11x, authenticate sending domains, connect CRM and calendar, start domain warm-up |
| 3 | Sales + RevOps | Launch 80/20 parallel pilot, validate reply rates and meetings booked, compare to Apollo baseline |
| 4 | Sales + RevOps | Migrate sequences one at a time, monitor performance, adjust messaging and routing as needed |
| 5 | RevOps | Complete cutover, disconnect Apollo integrations, repoint sending domains, archive reply history |
| 6 | Procurement | Submit offboarding request, confirm data deletion, update vendor records, finalize contract cancellation |
Common migration pitfalls
Skipping domain warm-up. This is the single biggest deliverability risk. Sending cold emails through a new domain without a 14-day warm-up drops reply rates by 15–25% and increases spam-folder placement. Always complete the warm-up before migrating live volume.
Big-bang cutover. Migrating all sequences at once almost always causes a 2–3 week reply-rate dip. Reps lose familiarity with the new platform, sequences don't perform as expected under load, and troubleshooting becomes impossible because too many variables changed at once. Migrate sequence by sequence over 1–2 weeks instead.
Missing the auto-renewal notice window. Apollo's contracts reportedly require 60–90 days' notice to cancel, based on third-party reports. If you miss the window, you're locked into another year. Surface the contract terms in week 1 of the migration and set a calendar reminder for the notice deadline.
Underestimating field-mapping complexity. Custom CRM fields rarely map 1:1 across platforms. Apollo's ICP_Score field may not exist in 11x, and 11x's Intent_Signal field may not exist in Apollo. Build a mapping table in week 1 and validate it manually before bulk import. Most teams discover 2–3 fields that require manual rebuild.
Migrating during a quota period. Sales reps will resist migration if it happens mid-quarter or during a high-stakes pipeline push. Plan the migration for a planning week, early in the quarter, or during a low-activity period (end-of-year holidays, summer). RevOps should align with the sales leader on timing in week 1.
Forgetting the data-deletion request. If you don't explicitly request data deletion under GDPR or CCPA, your contact list remains in Apollo's system indefinitely. This creates compliance risk and leaves your data exposed to potential breaches. Include the data-deletion request in the offboarding email and get written confirmation.
Final verdict on migrating from Apollo to 11x
Migration is non-trivial. It takes 4–6 weeks of real RevOps work, requires stakeholder alignment across five teams, and carries deliverability risk if domain warm-up is skipped or cutover is rushed.
Apollo provides genuine value to teams that fit its ICP—particularly teams that need a large contact database, email-and-LinkedIn sequencing, and a self-serve onboarding model. Teams that are happy with Apollo should stay.
For teams that have decided to leave—because of renewal pricing, capability gaps (inbound voice, multilingual), or deliverability issues—the parallel-pilot approach (Steps 2–3) is the lowest-risk path. Running both platforms side-by-side for 2 weeks allows you to validate 11x performance against the Apollo baseline before committing to full cutover. Most teams see parity at week 2 and meaningful upside (10–20% higher reply rate, 15–25% faster time-to-meeting) at weeks 4–6.
Frequently asked questions about migrating from Apollo
How long does it take to migrate from Apollo to 11x?
4–6 weeks for most teams, including a 2-week parallel pilot. Week 1 is inventory and export. Week 2 is 11x setup and domain authentication. Weeks 3–4 are the parallel pilot. Weeks 5–6 are cutover and contract cancellation. Teams with 10+ sequences or complex CRM integrations may need 7–8 weeks.
Will I lose my sequence templates?
No, but you'll need to rebuild them manually. Apollo does not provide a bulk export for sequences. Each sequence must be copied step-by-step into a spreadsheet or Google Doc, then rebuilt in 11x's sequence editor. A 7-step sequence takes 15–20 minutes to document and rebuild. Teams with 10+ sequences should allocate 3–4 hours for this step.
Will my deliverability drop?
It can drop 10–15% temporarily if you skip domain warm-up or rush cutover. The mitigation is a 14-day staggered warm-up with SPF, DKIM, and DMARC authentication, followed by a gradual volume ramp. Most teams see deliverability return to baseline within 7–10 days of completing warm-up. Teams that skip warm-up see a 15–25% drop that persists for 3–4 weeks.
Can I run Apollo and 11x in parallel?
Yes, and this is the recommended approach. Running both platforms in parallel for 2–4 weeks allows you to validate 11x performance against the Apollo baseline before committing to full cutover. The 80/20 split (80% on Apollo, 20% on 11x) is the most common pilot design. Most teams keep Apollo active until all sequences are migrated and performance is validated.
What happens to my Apollo contract during migration?
Apollo's contracts reportedly include auto-renewal clauses with 60–90 day notice windows, based on third-party reports. If you're inside the auto-renewal window, you may be locked into another year unless you negotiate an early-termination fee. Review the contract in week 1 of the migration and submit the cancellation notice as soon as the decision to migrate is final. Most teams submit the notice in week 1 and complete offboarding in week 6.
Does 11x include onboarding support for migration?
Yes. 11x provides a dedicated CS resource for onboarding, including domain authentication, CRM field-mapping, sequence rebuild, and parallel-pilot design. The CS resource is included in the contract and typically engages for 4–6 weeks during the migration. Most teams complete onboarding in 2–3 weeks with CS support.
What if my CRM has custom fields that don't map?
Build a mapping table in week 1 that shows Apollo field names, data types, and the corresponding 11x field (or note where a new field must be created). Most teams discover 2–3 fields that don't map cleanly. These fields require manual rebuild in 11x or in the CRM. Allocate 2–4 hours in week 3 to recreate the logic. 11x's CS team can assist with complex field-mapping scenarios.
How does 11x compare to Apollo after migration?
11x positions Alice (AI SDR for outbound) and Julian (AI phone agent for inbound) as a unified platform for outbound and inbound motion. Alice handles email, LinkedIn, and multi-channel sequencing in 105+ languages, which covers ICPs that Apollo does not natively support. Julian handles inbound phone qualification with sub-60-second speed-to-lead, which Apollo does not offer. 11x includes a native 400M+ verified contact database, which may replace some of Apollo's enrichment subscriptions. Teams that need inbound voice, multilingual outbound, or faster time-to-first-meeting typically see the most value from the migration.
What are the most common reasons migration fails?
Skipping domain warm-up, attempting a big-bang cutover, missing the auto-renewal notice window, underestimating CRM field-mapping complexity, and migrating during a quota period. Each of these failure modes is preventable with proper planning in week 1.
Can I migrate just part of my Apollo setup?
Yes. Some teams migrate outbound sequences to Alice but keep Apollo for contact enrichment or list building. Some teams migrate only specific ICPs or geographies. The parallel-pilot approach allows you to test a subset of your Apollo setup in 11x before committing to full migration.
Last updated: January 2026.