O2C Integration and Data Migration Lead

## Role purpose Design and implement the technical movement of data across Salesforce, Intuit Enterprise Suite, the approved commercial connector, and related Order-to-Cash systems. Ensure that records move accurately, route to the correct entities and dimensions, avoid duplication, produce visible exceptions, and reconcile to approved source data. This role will work under the direction of the End-to-End O2C Program Architect and Delivery Lead and coordinate closely with the IES, Salesforce, Finance, data-quality, testing, and implementation workstreams. ## Key responsibilities - Define system ownership, integration direction, source-of-truth rules, and data lineage by object and field. - Translate the approved O2C process into connector mappings, routing rules, synchronization logic, transformation rules, and exception paths. - Configure the approved commercial connector for a three-entity operating model. - Map customer, account, item, order, invoice, credit, payment-status, entity, dimension, and other approved data. - Design duplicate-prevention, idempotency, retry, failure-visibility, and recovery controls within the connector's capabilities. - Evaluate and implement appropriate API, webhook, polling, batch, and event-driven integration patterns. - Configure authentication, credentials, environments, connection settings, and integration permissions in accordance with approved security requirements. - Analyze schemas, payloads, integration logs, error messages, and transaction traces. - Assess migration requirements and prepare mapping specifications, transformation rules, load sequences, validation procedures, and rollback plans. - Coordinate migration dependencies across Salesforce, IES, Finance, data-quality, and testing workstreams. - Execute or support trial migrations, production migration, reconciliation, defect correction, and cutover recovery. - Conduct volume, duplicate, routing, retry, exception, and failure-mode testing. - Promote approved configuration from test environments into production using controlled deployment procedures. - Identify requirements that cannot be met through the approved commercial connector and document practical alternatives. - Produce technical configuration records, support procedures, integration diagrams, data mappings, and handoff materials. - Escalate requirements that fall outside the approved integration architecture, connector capabilities, or workstream scope. ## Success in the role Approved data moves accurately and consistently across systems, transactions route to the correct entities and dimensions, duplicate creation is controlled, integration failures are visible and recoverable, and migration results reconcile to approved source data. ## Preferred background Select candidates with meaningful hands-on experience in: - Salesforce-to-accounting or Salesforce-to-ERP integrations - QuickBooks, Intuit Enterprise Suite, or comparable accounting-system integrations - Commercial integration platforms and connector configuration - REST APIs, webhooks, structured payloads, authentication, and data exchange - Customer, order, invoice, credit, payment, and item synchronization - Multi-entity and dimensional transaction routing - Field-level mapping, source-of-truth design, and data lineage - Idempotency, duplicate prevention, retry logic, exception handling, and recovery - Data migration, transformation, validation, and reconciliation - Test-environment configuration and production deployment - Integration testing, cutover, rollback, and stabilization - Technical documentation and operating handoff Candidates must have both integration and data-migration experience. Experience limited to basic CSV imports or general project coordination is not sufficient. ## Screening questions 1. Describe an integration you personally designed or configured between Salesforce and an accounting or ERP platform. Which records moved, what integration pattern was used, and how was source-of-truth ownership assigned? 2. How have you prevented duplicate customers, invoices, payments, or other financial records in a production integration? 3. Describe your approach to migration mapping, transformation, load sequencing, validation, reconciliation, and rollback. 4. Which commercial connectors, integration platforms, APIs, databases, or data-transformation tools have you configured directly? 5. Describe a production integration failure involving duplicate, missing, delayed, or incorrectly routed financial transactions. How did you isolate the cause, repair the affected records, and prevent recurrence?