Migrate from Beamery to Crelate

Beamery Contacts map to Crelate Contacts. Standard fields (name, email, phone, title, location) migrate directly. Multi-value fields use five-semicolon delimiters in Beamery exports; we re-encode these as Crelate multi-select picklist values before load. We deduplicate Beamery Chrome Extension duplicates by running Beamery's deduplication process before export. Custom fields on Contact migrate as Crelate custom fields created during schema setup, with Beamery Single-Select mapped to Crelate picklist and Multi-Select mapped to Crelate multi-select picklist.

Beamery Talent Pools are named collections with membership dates. We map each Beamery Talent Pool to a Crelate Tag (for the pool name) and a Crelate Group (for membership tracking). Pool membership dates migrate as a custom date field on the Contact record. The customer chooses during scoping whether to use Tags, Groups, or a combination based on their ongoing engagement workflow.

Beamery Vacancies map to Crelate Job records. We export vacancy metadata (title, department, location, status, pipeline stage) and linked candidate assignments. Beamery pipeline stage names vary by tenant; we capture the customer's specific stage labels during scoping and map them to equivalent Crelate pipeline stages during migration. Vacancy-to-candidate linkage migrates as a Crelate Job-Contact association.

Beamery Campaigns are outbound engagement sequences with membership and send dates. We export campaign membership and engagement events (send dates, open events, click events) and link them as Activity records against the corresponding Crelate Contact. The campaign automation logic (Recipe triggers and conditional actions) is documented separately as non-portable.

Beamery Skills are taxonomy entries attached to Contacts. Beamery's skills taxonomy is customer-defined. We export all assigned skills as flat text tags and load them as Crelate Tags on the Contact record. If the customer has a structured skills taxonomy with parent-child relationships, we preserve the hierarchy in a custom field or as a delimited text field in Crelate.

Beamery Convert Flows are forms that create Contacts. We preserve submitted field data and conversion timestamps from Beamery's form submission records. The Convert Flow configuration itself (form builder, field logic, routing rules) is not portable and must be rebuilt in Crelate. We document the existing form fields and routing logic for the customer's admin to rebuild in Crelate's form builder.

Beamery Users (recruiters and sourcers) map to Crelate Users by email address. We export user IDs, names, roles, and ownership assignments during scoping. Role names and permission levels differ between platforms; mapping is done per-customer during scoping with the customer's admin. Users without a matching Crelate User are held in a reconciliation queue for admin provisioning before record import.

Beamery custom fields (Single-Select, Multi-Select, Short Text, Date) on Contacts and other objects are discovered via the Beamery API before export. We create equivalent Crelate custom fields during schema setup: Beamery Single-Select maps to Crelate picklist, Beamery Multi-Select maps to Crelate multi-select picklist, Beamery Short Text maps to Crelate text, and Beamery Date maps to Crelate date. Multi-value delimiters in Beamery Multi-Select exports use five semicolons; we re-encode to Crelate's multi-select format before load.

Beamery engagement events (emails sent, page views, notes, calls, meetings) are timestamped activities linked to Contacts. We export them as a separate activity log and link them back to the corresponding Crelate Contact record with the original timestamp preserved. Engagement type maps to Crelate Activity type. Campaign membership events from Beamery Campaigns migrate as Activity records attached to the relevant Contact.

Beamery Experience records (work history entries on a Contact) are exported from the experience file in Beamery's flat-file format. We map them to a Crelate custom section on the Contact record or to a linked Experience custom object if the customer configures one. Employment dates, title, company, and description migrate as custom fields.

Beamery Education records are exported from the education file in Beamery's flat-file format. We map them to a Crelate custom section on the Contact record or to a linked Education custom object. Degree, institution, graduation date, and field of study migrate as custom fields.

Beamery Notes attached to Contacts migrate to Crelate Notes linked to the Contact record. Note body, author, and timestamp preserve. If Beamery notes contain attachments, we migrate the attachment URL as a custom field reference; actual binary file retrieval depends on whether the storage is accessible via API.

Beamery attachments (resumes, portfolio files) are stored as references in Beamery. We export the file URL and metadata from the attachments file. Actual file retrieval depends on whether the storage is accessible via API or requires manual download. We flag any attachments that cannot be retrieved via API for manual handoff to the customer.

Beamery Recipes are event-driven automation rules referencing internal IDs and trigger logic that are not portable across platforms. We document the active Recipe configuration during scoping (trigger conditions, actions, downstream effects) so the customer can manually rebuild equivalent automations in Crelate's workflow builder (available at Business Plus tier). Recipes do not migrate as code.

Beamery Pages are hosted career site configurations that cannot be exported as structured data. We document the existing page URLs and advise rebuilding the career site in Crelate's Branded Job Portal feature (included in Business tier). Page content, branding, and job posting templates require manual rebuild.