Migrate for a structural reason. Frustration is not one, and it follows you.
That company had a migration quoted before we read the system. The object model was fine; the matching rules were not. Rebuilding in place cost a fraction of the quoted migration and did not carry the old model onto a new platform.
When the object model genuinely cannot represent how you sell, when a merger forces consolidation, or when licensing economics have broken. Frustration with configuration is not a reason, because it follows you.
No. A migration carries the existing data model unless somebody redesigns it, so duplicates, blank sources and unclear stages arrive on the new platform intact.
Write down what you cannot model today. If the answer is a process or a field, it is configuration. If it is the shape of the objects themselves, it may be the platform.
All of it free.
Leave an email and I will reply myself, usually the same day. No sequence, no newsletter, and no calendar link unless you ask for one.
Would rather just book time? Here is the calendar.
We use cookies to run the site and to understand how it is used. You can accept all or necessary only. See our privacy notice.