Migrate from Oracle Field Service Cloud to Mailchimp

Oracle Field Service stores customer contact records associated with accounts and service locations. These map directly to Mailchimp contacts within an audience. Email address is the required identifier for Mailchimp; contacts without email in OFSC require a placeholder or are flagged for manual review before migration.

OFSC Accounts are corporate entities with multiple contacts and service locations. Mailchimp has no Account object — we map each Account to a Mailchimp Audience and attach all related contacts to that audience. If multiple OFSC accounts share the same domain or brand, they may be consolidated into a single audience based on your specification.

OFSC Service Locations contain address, city, state, postal code, and country for each service point. We merge these into Mailchimp's standard ADDRESS merge field on the associated contact. Contacts with multiple service locations are handled by creating a primary address as ADDRESS and storing additional locations as comma-separated text in a custom merge field.

Any custom fields defined on the OFSC Account record (e.g., contract tier, SLA level, billing account number, industry classification, or regional cost center codes) are extracted and mapped to Mailchimp audience-level merge fields. These audience merge fields appear on every contact within the associated Mailchimp audience, allowing segmentation and personalization based on account-level attributes without requiring per-contact field population. If a custom property is marked as contact-specific in OFSC, we treat it as a contact merge field instead.

OFSC contact-level custom properties (e.g., preferred contact method, customer since date, account manager) map to Mailchimp contact merge fields. Merge field data types are inferred from OFSC field types — date fields become TEXT in Mailchimp since merge fields do not support date picker.

OFSC system timestamps (created, last modified) are preserved as custom text merge fields on the Mailchimp contact record. Mailchimp's native member since date reflects the migration import date, not the original OFSC creation date — we store the original date for reporting continuity.

Oracle Field Service Resources represent field technicians, dispatchers, and administrators. Mailchimp has no equivalent — we optionally migrate internal Resources as contacts with a 'internal_resource' tag so they can be excluded from marketing campaigns or used in internal newsletters. Scheduling, skills, and capacity data do not map to Mailchimp.

OFSC Activities are work orders with status, time entries, parts used, and technician assignments. Mailchimp has no work order or service activity schema. Activity history is not migrated — it has no place in an email marketing platform. If activity history is business-critical, export OFSC reports separately before migration.

OFSC manages parts and inventory linked to activities, tracking stock levels, warehouse locations, and component relationships for service work orders. This inventory model includes bin locations, reorder thresholds, and parts consumption history tied to specific technician activities. Mailchimp has no inventory model — it operates purely as a contact and campaign management system without any product, stock, or supply chain schema. Inventory data, parts listings, and stock level information cannot migrate because Mailchimp provides no destination structure for this operational data.

OFSC Skills and Certifications attached to Resources can be extracted and applied as Mailchimp tags on Resource contacts. For example, a technician with 'HVAC Certified' skill becomes a contact tagged 'HVAC_Certified'. This is informational only — Mailchimp cannot use these tags to trigger scheduling or assignment logic.

OFSC Routes and Buckets control daily dispatch scheduling and technician capacity, organizing work orders into logical sequences, optimizing travel paths, and balancing workload across field resources based on geographic proximity, skill certifications, and availability windows. Mailchimp has no routing, scheduling, or capacity model — it lacks any mechanism for work order sequencing, technician dispatch, geographic optimization, or resource load balancing. These operational constructs, including route definitions, bucket assignments, and capacity constraints, cannot migrate because Mailchimp provides no equivalent schema or automation trigger for field service scheduling logic.

OFSC Workflow Manager defines step-by-step guided processes for field technicians. Mailchimp's Customer Journeys are campaign-triggered automations (e.g., 'tag added → send welcome email'). The logic and structure are fundamentally different — we export OFSC workflow definitions as a reference document for manual rebuild, but no automated conversion is possible.

OFSC SLA Rules define response time and resolution time commitments tied to work order priority. Mailchimp has no SLA construct. SLA data is preserved as text in a custom merge field for reference but has no operational effect in the destination.

Files attached to OFSC contact or account records are downloaded and re-uploaded to Mailchimp's Asset Library. File size limits apply (Mailchimp supports up to 400MB per file). Attachments related to work orders or activities are not migrated as there is no corresponding context in Mailchimp.