WorkSpan AWS Partner Central API Migration

Prerana Gupta

Created July 01, 2026 13:39. Last Updated July 01, 2026 15:22

AWS Partner Central API Migration Briefing

Action required for WorkSpan Co-sell with AWS customers using the legacy AWS S3-based CRM integration.

Action Required Complete migration to AWS Partner Central APIs	Deadline Before September 30th, 2026
Primary Risk Loss of AWS opportunity and lead synchronization	Expected Migration Time Typically 2–4 hours, including testing

Already on the Partner Central APIs?
If your organization went live with WorkSpan Co-sell with AWS after January 2025, you are already using the AWS Partner Central APIs and no further action is required. You may disregard this communication.

Dear Valued Customer,

AWS has announced the retirement of the legacy S3-based CRM integration used for AWS Partner Central opportunity and lead synchronization. If your organization has not yet migrated to the AWS Partner Central APIs for Selling, action is required.

This communication is a continuation of WorkSpan's previous notifications, including our communication sent on July 24th, 2025. WorkSpan has previously reached out to customers to begin planning and scheduling this migration. AWS has now issued updated sunset dates for the legacy S3 integration, making it important to complete any remaining migrations well before the deadline.

Executive summary: Customers that complete the migration protect AWS co-sell continuity, remain aligned with AWS's supported integration model, and avoid disruption when the legacy S3 integration is retired. This API migration is separate from APN migration activity and should be completed first.

Why You Are Receiving This

You are receiving this notice because your organization has used, or may still be using, the legacy AWS S3-based CRM integration for AWS Partner Central through WorkSpan.

The purpose of this communication is to clearly outline:

What AWS is changing.
What action your organization needs to take.
The key deadlines and operational impact.
The expected migration effort.
The difference between API migration and APN migration.
How WorkSpan will support your migration.

What Is Changing

The legacy S3-based CRM integration is being retired. Once AWS ends support, S3 inbound processing will stop accepting files and outbound opportunity and lead synchronization will be discontinued.

To maintain AWS co-sell continuity, customers still on the legacy integration must migrate to the AWS Partner Central APIs for Selling.

API Migration vs. APN Migration

The AWS Partner Central API migration and any APN migration activity are different workstreams. The API migration specifically replaces the legacy S3-based CRM integration with the supported Partner Central API integration for opportunity and lead synchronization.

If your organization also has APN migration activity, the recommended sequence is: complete the API migration first, then manage APN migration as a separate follow-on activity.

Confirmed Timeline

Date	What Happens	Customer Impact
Today	Confirm your migration status and schedule your migration if not yet complete.	Allows time for planning, validation, testing, and go-live readiness.
Before September 30th, 2026	Complete migration to the AWS Partner Central APIs.	Maintains continuity of AWS co-sell opportunity and lead synchronization.
September 30th, 2026	S3 inbound processing stops accepting files and outbound sync is discontinued.	Your CRM will no longer send or receive AWS Partner Central updates through the S3 integration.
October 30th, 2026	AWS revokes access to S3 buckets.	Any required historical data should be downloaded before this date.
December 31st, 2026	AWS begins decommissioning S3 buckets.	Partners lose access to pipeline data stored within the legacy buckets.

Business Impact: If You Migrate vs. If You Do Not

If You Complete the Migration	If You Do Not Complete the Migration
Continue AWS opportunity synchronization through the supported API model.	Opportunity synchronization through S3 stops after the AWS deadline.
Continue lead synchronization between WorkSpan, your CRM, and AWS Partner Central.	Lead synchronization through the legacy S3 integration is discontinued.
Remain aligned with AWS's strategic integration direction.	Your organization remains dependent on an unsupported legacy integration.
Reduce migration uncertainty by completing the API migration before any separate APN migration activity.	Risk confusion between API and APN migration workstreams, creating delays or sequencing issues.
Benefit from WorkSpan migration guidance, validation, and go-live support.	Risk late migration pressure, compressed testing windows, and operational disruption.

Why This Migration Should Be Prioritized

1. AWS S3 Sunset Creates an Operational Deadline

The S3 deprecation timeline creates a clear technical deadline. After September 30th, 2026, the legacy S3 integration will no longer support inbound files or outbound synchronization. Customers that do not migrate risk disruption to AWS co-sell workflows, opportunity updates, and lead processing.

2. API Migration and APN Migration Are Separate Workstreams

Some partners have asked whether the Partner Central API migration is the same as an APN migration. They are different migration activities.

The recommended sequence is to complete the API migration first, so your opportunity and lead synchronization is moved from the legacy S3 integration to the supported Partner Central API model. Any APN-related migration activity should then be handled as a separate follow-on workstream.

PRM Note

AWS continues to emphasize the importance of clean partner operations and reporting readiness, including PRM-related requirements. This communication does not imply a direct dependency between APN migration and PRM. Completing the API migration helps ensure your AWS co-sell integration remains stable and aligned with AWS's supported operating model.

Benefits of Migrating

Maintain uninterrupted AWS co-sell operations by migrating before the S3 retirement deadline.
Clarify migration sequencing by completing the Partner Central API migration first, before handling any separate APN migration workstream.
Improve operational efficiency through a modern API-based integration model.
Increase resilience with improved validation, monitoring, and recovery capabilities.
Enable future AWS innovation by aligning with the supported Partner Central API framework.

What to Expect During Migration

WorkSpan will guide your team through the migration process. The expected migration activity, including testing, should typically be completed within 2–4 hours, assuming prerequisites are in place and customer stakeholders are available.

A typical migration includes:

Migration planning – Confirm current integration status, prerequisites, and target timing.
Configuration updates – Enable and configure the Partner Central API integration.
Validation – Confirm mappings, sync behavior, and required integration settings.
Testing – Validate opportunity and lead flows before production cutover.
Production cutover – Move from the legacy S3 integration to the Partner Central APIs.
Post-migration verification – Confirm successful sync and operational readiness after go-live.

WorkSpan Migration Guidance

WorkSpan has published migration guidance to help customers complete the transition from the legacy S3 integration to the Partner Central APIs.

View the WorkSpan AWS Partner Central 3.0 API Guide for detailed migration instructions and readiness guidance.

What You Need to Do Next

1. Confirm your status: If your organization went live with WorkSpan Co-sell with AWS after January 2025, you are already using the AWS Partner Central APIs and no further action is required. You may disregard this communication. If you went live before January 2025, determine whether your organization has already completed the migration to the AWS Partner Central APIs.
2. Contact WorkSpan: If you have not completed the migration, contact your assigned CSM or support@workspan.com.
3. Schedule the migration: Secure a migration window with enough time for validation and testing before the AWS deadline.
4. Complete migration before September 30th, 2026: Avoid disruption to AWS opportunity and lead synchronization.

WorkSpan is committed to helping you complete this transition successfully, maintain uninterrupted AWS co-sell operations, and sequence any related APN migration activity correctly.

Best regards,
The WorkSpan Team

Footnote: If your organization went live with WorkSpan Co-sell with AWS after January 2025, or has already completed the migration to the AWS Partner Central APIs, you may disregard this notice.