Migration & Implementation Guide

Migrating to Audenci from other tools: Common sources: Hootsuite, Buffer, Sprout Social, Later, CoSchedule, Custom tools, Manual processes. Migration includes: Social account connections, Content library import, Historical analytics import, Team member migration, Process adaptation. Plan 2-4 weeks for full migration.

1. Export all data from current tool (posts, analytics, media)
2. Document current workflows and processes
3. List all social accounts to connect
4. Identify team roles and permissions needed
5. Create brand/organization in Audenci
6. Set up billing and subscription
7. Schedule migration timeline (dates, milestones)
8. Communicate plan to team

Set up Audenci foundation: Create organization and brands, Connect social accounts (start with primary accounts), Invite team members and assign roles, Configure settings: Timezone, Voice/tone, Categories, Pillars, Guidelines. Test post creation and publishing on sandbox account before production.

Import existing content and media: Export scheduled posts from current tool, Recreate high-priority posts in Audenci, Upload media library (organize in folders), Import historical analytics (via API or CSV), Set up campaigns for ongoing initiatives. Don't migrate: Old drafts (archive them), Completed campaigns (document learnings instead).

Import data via: CSV upload (bulk post creation, coming soon), API (programmatic import), Manual recreation (small datasets), Professional services (Enterprise, we migrate for you). Provide CSV with: Caption, Scheduled date, Platforms, Media URLs, Campaign, Category. API docs: api.audenci.com/import

Train team on Audenci: Conduct live onboarding session (2 hours), Assign role-based tutorials from Tutorial Hub, Schedule follow-up Q&A session, Create internal SOPs for your workflows, Set up Slack/email notifications, Schedule daily check-ins first week. Common training areas: Post creation with wizards, AI features, Approval workflows, Calendar management, Analytics dashboard.

Run both tools in parallel: Continue publishing from old tool, Create all new content in Audenci, Test all workflows in Audenci, Monitor for issues, Compare analytics between tools, Identify and fix gaps. Parallel running builds confidence before full cutover.

Cut over to Audenci: Disconnect social accounts from old tool (prevents duplicate posts), Verify all accounts connected in Audenci, Publish first post from Audenci to production, Monitor publishing closely first 24 hours, Have rollback plan ready (reconnect to old tool if critical issues), Celebrate successful migration with team!

Optimize after go-live: Review workflows and refine, Set up automations to save time, Configure integrations (Slack, GA4, Zapier), Build custom reports, Train on advanced features, Gather team feedback, Document learnings, Archive old tool (after 30 days of successful operation).

Watch for these issues: Social account connection failures (expired tokens), Missing media (broken links from old tool), Incorrect timezone (check scheduled times), Permission issues (roles not configured correctly), Workflow confusion (team using old processes), Analytics gaps (historical data not imported). Address issues immediately - don't let them compound.

Enterprise customers get migration assistance: Dedicated Customer Success Manager, Migration project plan, Data import by our team, Custom training sessions, Parallel running support, Go-live assistance, 30-day post-launch support. Contact sales@audenci.com for Enterprise migration.

If critical issues occur post-launch: Reconnect social accounts to old tool, Reschedule posts there, Document Audenci issues, Contact support immediately, Fix issues before second attempt. Critical issues that require rollback: Posts not publishing, Analytics not syncing, Accounts disconnecting, Team unable to use features. Non-critical issues can be fixed while live.

Measure migration success: All social accounts connected (target: 100%), Team trained and onboarded (target: 100%), Posts publishing successfully (target: 100% success rate), Analytics syncing correctly (target: < 1 hour delay), Team satisfaction (survey: target > 8/10), Time saved vs old tool (target: 20%+ time savings). Review metrics at 30, 60, 90 days.

• Plan 2-4 weeks for full migration
• Start with 2-3 accounts, not all at once
• Train team before go-live
• Run both tools in parallel for 1-2 weeks
• Test on private accounts before production
• Have rollback plan ready
• Document workflows and processes
• Celebrate milestones and wins
• Request Enterprise migration support if available