Client Social Account Migration Checklist (Onboarding)
A checklist with 8 steps: Inventory every social profile the client owns before touching a single credential.
By InnovaAI ResearchPublished
Client Social Account Migration Checklist (Onboarding)
- 01
Inventory every social profile the client owns before touching a single credential
List all active and dormant accounts across networks, noting handle, URL, current admin access, and any linked business manager or CRM. This prevents orphaned profiles from being missed during migration.
- 02
Collect and verify login credentials and two-factor authentication methods for each profile
Use a secure password manager to store credentials, confirm 2FA is active, and document recovery options. Agencies must never store client passwords in plain text or shared spreadsheets.
- 03
Map each profile to the appropriate client workspace in the new platform
Create a separate workspace or client folder per brand, mirroring the agency's internal structure. This keeps retainer reporting clean and prevents cross-client content mix-ups.
- 04
Reconnect all third-party integrations, including analytics, ad accounts, and CRM tools
Verify that pixel data, conversion APIs, and any automation flows are pointing to the correct client properties. A broken integration here silently corrupts delivery metrics.
- 05
Audit existing content calendar and scheduled posts for conflicts or duplicates
Pull the last 30 days of scheduled content from the old tool and cross-check against the new calendar. Duplicate or orphaned posts waste client budget and erode trust.
- 06
Set up approval routing and role-based permissions for every team member
Define who can draft, approve, and publish for each client. Agencies should default to a two-step approval for paid or high-risk content, and restrict publishing to senior staff.
- 07
Run a parallel posting test for one week before fully switching over
Publish a low-stakes post through the new platform while keeping the old tool active. Compare timestamps, formatting, and link tracking to confirm the new system handles delivery correctly.
- 08
Document the migration and notify the client with a handoff summary
Provide a clear record of what moved, what changed, and any action items for the client. This closes the loop and sets expectations for the new operating rhythm.