Migrate from Selly Erp to Microsoft Dynamics 365 Business Central

Selly ERP Lead records map directly to Dynamics 365 Lead. We extract first name, last name, email, phone, company name, lead source, and status from the in-app export. The Lead record type and associated lead score or rating fields migrate as custom fields in Dynamics 365. Lead assignment rules in Dynamics 365 must be configured post-migration; we provide a written specification based on the Selly owner assignments observed during export.

Selly ERP Opportunities map to Dynamics 365 Opportunity. The opportunity name, estimated value, close date, stage, and owner transfer directly from the export. Stage probability percentages from Selly map to the corresponding stage probability in Microsoft Dynamics 365 Sales Process. We confirm the stage label mapping with the customer during scoping because Selly pipeline stages are customer-configurable and do not follow a universal naming convention.

Selly ERP Customer records carry both company-level and individual contact-level data within a single record. We split these into Dynamics 365 Account (company name, address, industry, annual revenue) and Contact (individual name, email, phone, job title, role) records linked by the AccountId lookup. The customer decides during scoping whether to split multi-contact customers into separate Contact records or collapse them to a single Account with one primary Contact.

Selly ERP Deals track pipeline positions and monetary values alongside Opportunities in the source system. We treat Deals as the primary monetary record and map them to Dynamics 365 Opportunity, preserving deal name, value, stage, owner, and expected close date. Where a Selly account has both an Opportunity and a Deal for the same transaction, we consolidate into a single Dynamics 365 Opportunity with the higher value and most recent stage.

Selly ERP allows custom pipeline stage names. We extract the complete stage list during scoping, including probability and order, and reconstruct these as a Microsoft Dynamics 365 Sales Process with corresponding stage values. Stage probability percentages map from Selly to Dynamics 365 StageProbability. If the customer has multiple Selly pipelines, each becomes a separate Sales Process in Dynamics 365, and we configure Record Types to route opportunities to the correct process.

Selly ERP invoice records are available as structured data in the export, but invoice PDFs are not reliably retrievable as rendered documents. We extract invoice header fields (invoice number, date, due date, customer reference, totals) as structured records and separately archive the original PDF for each invoice as a document attachment in Dynamics 365 SharePoint or as a Note with the PDF linked. Invoice line items migrate as Invoice Lines if the destination is Business Central, or as Sales Order Lines if the destination is Finance and Operations. Tax codes and payment terms require customer confirmation during scoping because Selly and Dynamics 365 tax configurations differ.

Selly ERP Quotes map to Dynamics 365 Quote. Quote number, expiration date, line items, totals, and discount percentages transfer directly. Custom quote templates configured in Selly do not transfer; we document the template structure (logo placement, line item formatting, terms) so the customer can recreate it using Dynamics 365 Quote Templates. Quote status (Draft, Sent, Accepted, Lost) maps to the corresponding Dynamics 365 status field.

Selly ERP activity records attached to Contacts, Opportunities, or Deals migrate to Dynamics 365 as Task (for calls and tasks), Email (for email engagements), Appointment (for meetings), or Note (for free-text notes). We normalize timestamps to the destination timezone and preserve the owner assignment. Activity type flags from Selly (call_disposition, meeting_location) migrate as custom fields on the corresponding Dynamics 365 activity record. Large activity volumes require batch processing through the Dynamics 365 Web API with pagination and exponential backoff on rate limit responses.

Selly ERP user accounts map to Dynamics 365 User records. We resolve Selly owners by email match against the destination User table. Any Selly owner without a matching Dynamics 365 User goes into a reconciliation queue for the customer's admin to provision before record import continues. Inactive or archived Selly users are provisioned as Dynamics 365 Users with a disabled license flag and are not counted toward the active seat total.

Custom fields defined on any Selly ERP object are extracted as-is during the manual export, including field name, data type, and values. We create matching custom fields in Dynamics 365 before importing data, mapping field types to the closest Dynamics 365 equivalent (text fields to Text, numeric fields to Number or Decimal, date fields to DateTime). Picklist-style custom fields in Selly map to Dynamics 365 Option Sets. Custom field labels and help text are preserved in the field configuration.

File attachments linked to Selly ERP records (proposals, images, contracts) are extracted from the export and stored separately for re-upload after record creation in Dynamics 365. We map each attachment to the corresponding record via SharePoint Document Location or a Note with the file attached. Attachments do not survive bulk CSV import in Dynamics 365; they require post-creation API upload or manual re-attachment, and we budget time for this step in the migration plan.

Selly ERP workflow rules, triggers, and automated sequences cannot be exported as structured data. We document every active automation observed during the discovery call — including trigger conditions, actions, and recipients — and produce a written specification that maps each Selly automation to a Power Automate flow or Dynamics 365 native workflow recommendation. The customer's admin rebuilds automations post-migration; this work is outside the migration scope.