🔧
Implementation and Integration
Data migration, integrations, and deployment strategies
⏱️ Estimated reading time: 18 minutes
Chapter 14: Implementation Strategy and Data Migration
Implementation Phases
Methodology
1. Discovery/Planning: Requirements, stakeholders, timeline
2. Design: Architecture, data model, security
3. Build: Configuration, development, customization
4. Test: UAT, regression, performance
5. Deploy: Change sets, metadata API
6. Hypercare: Intensive post-go-live support
Data Migration
Tools:
| Tool | Volume | Usage |
|---|---|---|
| Data Import Wizard | < 50K | Accounts, Contacts, Leads |
| Data Loader | < 5M | Any object |
| Bulk API | > 5M | Programmatic bulk loads |
Load order (respecting relationships):
1. Users (if they're record owners)
2. Accounts (parent)
3. Contacts (child of Account)
4. Opportunities (child of Account)
5. Opportunity Products
6. Activities (related to everything)
7. Notes & Attachments
Integration Patterns
| Pattern | Timing | Example |
|---|---|---|
| Request-Reply | Synchronous | Get stock from ERP when creating order |
| Fire-and-Forget | Asynchronous | Notify ERP of new order |
| Batch | Scheduled | Nightly invoice sync |
| UI Update | Real-time | Display external data in Salesforce |
Integration Tools
- Salesforce Connect: External Objects (live data without storing)
- Platform Events: Event-driven architecture
- MuleSoft: Integration platform (Salesforce company)
- REST/SOAP API: Direct integration
- Outbound Messages: Workflow-triggered notifications
Marketing Integration
- Pardot (Marketing Cloud Account Engagement): B2B marketing automation
- Marketing Cloud: B2C email marketing
- Lead scoring from marketing: Syncs with Salesforce leads
🎯 Key Points
- ✓ Load order: Users → Accounts → Contacts → Opportunities
- ✓ Data Loader for > 50K records
- ✓ 4 integration patterns: Request-Reply, Fire-and-Forget, Batch, UI Update
- ✓ Salesforce Connect shows external data without storing it
- ✓ Pardot = B2B marketing, Marketing Cloud = B2C