Migrate your Access CRM data

Contacts are the primary person-level record in Access CRM, holding name, email, phone, address, and owner assignment. Standard fields migrate 1:1 to most destination CRMs. We preserve any contact-level custom properties as custom fields on the target.

Companies (sometimes called Accounts in Access CRM configs) store business-level data linked to Contacts. The parent/child hierarchy migrates as a flat organisation tree, and we flag any circular references if they exist in the source data.

Opportunities carry Worst/Likely/Best monetary values and stage-based probability logic native to Access CRM. These map to Deals or Opportunities in destination CRMs, but the probability-calculation model differs — we recalculate stage probabilities against the destination's pipeline logic after import.

Access CRM's problem-tracking Cases support a lifecycle from open through resolution, with real-time routing to customer-service, warehousing, or accounts teams. Destination CRMs model ticket objects differently; we map case status and assignment history to the closest equivalent and flag any thread/comment data that may need flattening.

Access CRM exposes Kanban view pipelines with configurable stages. Pipeline stage names are free-text in Access CRM and often non-standard between tenants. We capture the full stage list during scoping and map them to destination pipeline stages, flagging any inactive stages that should be archived rather than migrated.

Custom fields are supported in Access CRM but their schema is tenant-specific and not self-documented in the admin UI. We extract the full field manifest via the admin knowledge base and cross-reference it against the CSV export to identify every non-standard field before mapping.

Enquiry forms capture leads directly from websites and feed them into Access CRM as Opportunities or raw leads. Form field structure is configurable; we treat each form as a custom object set and map its fields to the destination's lead or contact import schema.

Activities (calls, emails, notes) are associated with Contacts and Opportunities. Access CRM stores activity history in a threaded format. We flatten this to timestamped note records on the target object, preserving the original author and date.

Attachments on Contacts, Companies, and Opportunities migrate as file references pointing to the original upload location. We confirm that the destination supports file attachments on equivalent objects and flag any size or type restrictions.

Access CRM exposes a knowledge base for customer self-service. KB articles are content objects that do not have a standard counterpart in most CRMs. We export them as a structured export package rather than migrating them into CRM contact or ticket records.

User records (name, email, role) are migratable. We map the Access CRM owner/User assignment on each record to the corresponding user in the destination CRM, creating placeholder users if the destination does not yet have them provisioned.