Migrate from Re:Desk to Intercom

Re:Desk Member records map to Intercom Contact. The core contact fields (name, email, phone, address) migrate directly. Member-specific fields—membership type, expiration date, membership status—become custom attributes on the Contact record. If the destination Intercom workspace uses Companies, the member's associated household or organization becomes a Company record linked to the Contact. We preserve the original Re:Desk member ID in an external_id attribute for cross-system reference.

Re:Desk Programs (classes, leagues, activities) map to an Intercom Custom Object named Program. We define the Custom Object schema during scoping: program name, schedule, registration limit, pricing, instructor, and status fields. Each Program Custom Object record links to the Contact records of registered members via a many-to-many relationship. Intercom Advanced tier ($85/seat/month) or above is required for Custom Objects; we flag this during the edition review.

Re:Desk Facilities (courts, fields, rooms) map to an Intercom Custom Object named Facility. The schema captures facility name, type, location or address, capacity, and availability rules. Facility reservations link to Facility Custom Object records via a reservation-to-facility relationship. If the recreation data model includes different facility types (indoor courts, outdoor fields, pools), we add a facility_type attribute to the Custom Object schema.

Re:Desk Reservations (facility bookings, rentals, program registrations) map to an Intercom Custom Object named Reservation. Each record captures the reservation date range, time slot, associated member Contact, associated Facility, and status (confirmed, cancelled, completed). We create a dual-relationship schema linking Reservation to both the member Contact and the Facility Custom Object. Past and cancelled reservations migrate if scope includes historical data.

Re:Desk POS Transactions (concessions, registration fees, rental charges) map to an Intercom Custom Object named Transaction. Transaction records include timestamp, line items, payment method, amount, and associated member Contact. Intercom has no native financial or invoicing capability; Transaction records serve as a reference log for agents handling billing inquiries rather than a financial ledger. We preserve transaction metadata as read-only attributes on the Custom Object and note that the full transaction history may require a separate export for accounting purposes.

Re:Desk staff accounts (Administrator, Staff, Front Desk roles) map to Intercom Admins and Agents. We match staff by email address. Role mapping requires judgment: Re:Desk Administrators map to Intercom Admins (full workspace access); Re:Desk Staff and Front Desk map to Intercom Agents (inbox and conversation access). We flag any Re:Desk staff accounts that lack valid email addresses for reconciliation before Intercom provisioning.

Re:Desk Attendance records (limited by the platform's check-in/out constraints) map to an Intercom Custom Object named Attendance linked to the relevant Program and Contact. Given that Re:Desk's attendance functionality has known limitations, we flag gaps in the attendance data during scoping and preserve available records with a data completeness note. Attendance records do not map to Intercom Conversations or Tickets because they represent facility usage rather than support inquiries.

Re:Desk Invoices map to an Intercom Custom Object named Invoice primarily as a reference for agents handling billing disputes. Invoice records preserve invoice number, date, status (paid, pending, refunded), total amount, and linked Contact. The Invoice Custom Object does not replace a financial system; agents use it as a lookup during support conversations to verify payment history. We coordinate with the customer to determine which Re:Desk invoice statuses map to Intercom-readable labels.

Re:Desk organizations with custom fields on Members and Programs require Intercom custom attributes. We discover all custom field definitions during scoping—field name, data type (text, date, number, dropdown), and any conditional visibility logic—and create matching Intercom custom attributes. For custom fields on Programs, we add attributes to the Program Custom Object schema. Multi-select Re:Desk fields map to Intercom multi-select attributes.

Documents attached to Member records, Programs, or Reservations in Re:Desk export as binary blobs. We preserve filenames and association metadata. In Intercom, attachments to Contact records can be stored as note attachments or linked via a custom attribute pointing to an external document store URL. We do not guarantee that binary attachments render identically in Intercom; we recommend an external document repository strategy for recreation program waivers, membership agreements, and facility use contracts.